powered by CADENAS

Manual

Manual

5.8.2.1.3.  New link

The function New link is primarily meant for parts which are stored several times in different directories. (This could be accessories, but don't 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 function New link is also the best approach if projects had been created as real physical duplicates. Such projects cause an error message during QA check, because the standard name may not be the same in different projects. See Section 6.8, “Error Messages: Problem - Solution (PARTproject)” -> point "In project is the same standard name".

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 same NB NB='Cube 1 - $L.' and same table values

In above example we have duplicates.

Situation afterwards: The project "project1.prj" is multiply used and stored in the central folder "common". Link projects in "folder1" and "folder2" access the central "real" project.

Approach in order to eliminate duplicates:

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

  2. Delete duplicates at all other places.

  3. On a directory where you want to create a link project, click on the context menu command New link.

    -> The dialog box Choose project is opened.

  4. In the DATA directory, browse to desired project and click Open.

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

  5. In order to test created projects in PARTdataManager, the display index has to be created. Select a superordinated folder and click on the button Update index .

  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 directory "common" can be hidden for the PARTdataManager view (Hide directory).

Basic information on the Standard name can be found under Section 7.12.7.3, “ Guideline for NB, SHORTNB, LINA definition and Identification type ”.

[Note] Note

If not all rows of a link project are valid, use filters. On this see subpoints Restricted display and Restricted display in value ranges).

[Note] Note

If entire directories are to be linked, conduct this change in the dir.def with following syntax.

Link=..\..\xxx\verzeichnis

Delete link to project

If you wish to delete a link, click on Delete link to project in the context menu.

Restricted Display:

Optionally, you can specify a table restriction (rows) for link projects. Hereto, in the input field Restricted Display, use Fortran syntax (see Section 16.2, “Constants, Functions, Operators, mathematical expressions ”).

In PARTdataManager, only allowed table rows are displayed then.

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 in value ranges:

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

General syntax:

Row restriction ; value range restriction ; value range restriction

[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 original the variable "SEL" includes the values from 1 to 5

    PARTdesigner: In original the variable "SEL" includes the values from 1 to 5

    PARTproject: Link project restricts the value range variable "SEL" to the values 1 to 3

    PARTproject: Link project restricts 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

Also compare Links to parts under Section 5.9.3, “ Tabbed page 3D project ”. (Similarity in name but different purpose)