5.8.2.1.3.  New link

The New link function is primarily intended for parts that occur repeatedly in different directories. (These can be accessories, but do not have to be)

It is recommended to create a central folder (also multiple) in order to collect all parts multiply used. This minimizes the size of the catalog and results in more clarity.

When needed, links to these parts centrally managed can be created from any directory.

The New link function is also the best solution if projects have been created as real physical duplicates. Such projects cause an error message during the QA check, as the standard name must not be the same for different projects. See Section 6.8, “Error Messages: Problem - Solution (PARTproject)” -> Point "The project has the same standard designation".

Example

Situation before:

Project 1 with NB='Cube 1 - $L.'

project1.prj and project2.prj are duplicates

project1.prj and project2.prj are duplicates

Project 2 with the same NB NB='Cube 1 - $L.' and the same table values.

In above example we have duplicates.

Situation afterwards: The project "project1.prj", which is used several times, is located in the "common" folder. Link projects in "folder1" and "folder2" access the central "real" project.

Procedure for resolving duplicates:

  1. Create a central folder (in above example "common") and copy duplicate projects there.

  2. Delete duplicates at all other places.

  3. Click the New link context menu command in a directory in which you want to create a link project.

    -> The Select project [Choose project] dialog box opens.

  4. Browse to the desired project in the DATA directory and click Open.

    -> The link project is created and is marked with a blue arrow under Project selection under Project selection. The path to the "real" project is entered under Edit project -> General tab -> Link.

  5. To be able to test the projects created in the PARTdataManager you must create the display index. Select a higher-level directory and click on the Update index button.

  6. Open PARTdataManager.

    -> Now you will see the real project under "common" and the link projects under "folder1" and "folder2". A project's "true" storage location can be seen in the title bar at the very top.

    The "common" directory can be hidden by default for viewing in PARTdataManager ( Hide directory ).

Basic information on the standard designation [Standard name] can also be found under Section 7.17.9.3, “ Guideline for NB, SHORTNB, LINA definition and type identification ”.

[Note]Note

If a link project is not valid for all rows, filters can be used. See the subsections Table restriction and Table restriction in value ranges).

[Note]Note

If entire directories are to be linked, make this adjustment in the file dir.def with the following syntax.

Link=..\..\xxx\verzeichnis

Delete link to project

If you want to remove a link again, click the Delete link to project command in the context menu.

Table restriction [Restricted display]:

Optionally, you can also define a table restriction (rows) for link projects. To do this, use Fortran syntax in the Table restriction [Restricted display] input field (see Section 14.2, “Constants, Functions, Operators, mathematical expressions ”).

In the PARTdataManager only the permitted table rows are then displayed.

Example:

  • D (Nominal thread) > 10

    PARTproject: Parts with D > 10

    PARTproject: Parts with D > 10

    PARTdataManager: Parts with D > 10

    PARTdataManager: Parts with D > 10

  • D (Nominal thread) < 10

    PARTproject: Parts with D < 10

    PARTproject: Parts with D < 10

    PARTdataManager: Parts with D < 10

    PARTdataManager: Parts with D < 10

Restricted Display [Restricted display] in value ranges:

Optionally, you can combine a row restriction with a value range restriction:

General syntax:

Zeileneinschränkung ; Wertebereichseinschränkung ; Wertebereichseinschränkung

[Note]Note

Optionally, several value range restrictions can be stated separated by semicolon.

Examples:

  1. Row restriction:

    TYPE.EQ.'A'

  2. Row restriction in combination with value range restriction:

    TYPE.EQ.'A';HUB=10,20,30,40;HUBST=30,40

  3. Value range restriction without row restriction

    [Note]Note

    If there is no row restriction, but only a value range restriction, anyway the semicolon has to be set at the beginning.

    PARTdesigner: In the original, the variable "SEL" has the values 1 to 5

    PARTdesigner: In the original, the variable "SEL" has the values 1 to 5

    PARTproject link project filters the value range variable "SEL" to the values 1 to 3

    PARTproject link project filters the value range variable "SEL" to the values 1 to 3

    ;SEL=1,2,3

    PARTdataManager: Original project

    PARTdataManager: Original project

    PARTdataManager: Link project restricted

    PARTdataManager: Link project restricted

See also links to parts [Links to parts] under Section 5.9.4, “Tabbed page: Views ”(similar name but different purpose)