political relations

[ApeGana]

Bye.

use sev19. I need to reorganize the cad archive, changing path, folder names etc...

Before we begin, I am trying to understand a little better the policy of link resolution; that is where and with what logic if he goes to search for a linked file before telling you that he does not find it.

I found in an old thread the description of how the linkmgmt.txt file works, but honestly I understood little.
Can someone better explain to me the "container, relative and absolute" speech?

Thank you. ape

resolution of document links
when moving documents from one location to another, some of the links to documents may be interrupted. solid edge provides an ascii text file that contains useful information to resolve links. linkmgmt.txt contains information that allows you to specify search orders and search for an algorithm that defines folders during connection resolution.

By default, the linkmgmt.txt file is located in the program folder of solid edge. For example, if solid edge has been loaded on the c drive, the path will be c:\program files\solid edge\program\linkmgmt.txt.

you need to ask solid edge to search for the linkmgmt.txt file. You can make sure that solid edge searches for the file in a different folder, including those of another computer on the network. to do this, click options in the tool menu. in the File Positions tab of the Options dialog box, select File Properties linkmgmt and click on change. in the browse dialog box, specify the drive and directory that contains the linkmgmt.txt file.

to edit the file, use a text editor, for example note block. review the following linkmgmt.txt file of example.

container
relative
absolute
begin search path
c:\my documents
\\machine123\my documents
end search path




the keywords container, relative and absolute in the linkmgmt.txte file indicate the method and order in which the links are resolved. container search the files in the same folder of the container document. relative search files related to the container document at the time of positioning or saving. absolute search for the exact path for files when positioning or saving. reorder or remove keywords from linkmgmt.txt file to improve performance in link resolution.

if you are not sure of the existence of the document, you can add search paths to the linkmgmt.txt file. the directories listed among the keywords begin search path and end search path will be used to search for links. solid edge searches all subfolders placed in the folders indicated. the connection is resolved just with the finding of a document provided of the same name.

the linkmgmt.txt file is read with opening documents. changes made to the linkmgmt.txt file have no effect on any document opened at that time. to insert the desired changes, close and reopen the documents.

use search paths only when you will not be able to solve the connections using the container methods, relative, or absolute. if you search for paths is included in the linkmgmt.txt file, solid edge will search documents in such folders, which could adversely affect performance. to stop using search paths you can edit, delete or rename the linkmgmt.txt file..

 

[vespa_83]

honestly I have never tried to change linksmgmt.txt
So you should try.

reading the post I mean:
- container: if the b file is connected to the a file, (and a and b are in the same folder, if you move "set" files a and b)*, when you open b the link to a is searched first in the folder that "contains" b.
* maybe this doesn't fit and it must be omitted.

- Absolute usually means that if the folder is "\\server_a\folder_b\folder_c\file_d.ext" that is and that must remain.

- relative: it is not very different from container, but it exploits the relative routes, I presume only to descend for simplicity, or in the operating systems the paths are defined as absolute or relative, and here I think they exploit the same principles:
<percorso base="" di="" radice="">\file_b connected to <percorso base="" di="" radice="">♪
even here if you change <percorso base="" di="" radice=""> but leave the file name unchanged and the subfolder name, then the link is resolved.

as you see aside moving everything on a root folder, do very little (in safety).


do order by renaming everything and moving everything even if it seems a good thing is often a madness, I suggest to be followed by an expert who has a strong knowledge of the revision manager or takes advantage of an ad hoc programming</percorso></percorso></percorso>

 

[ApeGana]

Thank you vespa,
In the meantime, I did some evidence. substantially the meaning of container/relative/absolute is what you say, except for relatives that it also works "to rise" if the number of levels to rise is the right one.
in practice, if in your example we had:
<percorso base="" di="" radice="">* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
and
<percorso base="" di="" radice="">♪<serie cartelle="" dentro="" di="" l'altra="" n="" una="">\file_b
with file_b pointing to file_a, the link continues to work even if you change the names of n folders, as long as they remain n (no more, or less)
clearly if you change the folder name1 no longer works.

moreover the container priority sequence --> relative -- absolute is the default of if in case the linkmgmt.txt has not been addressed in the file options/positions.

in many years of use of if I had never noticed of this relative pointing system.

Unfortunately several important changes to the structure of the archive are forced to do them and I am aware that it will be a workmanship. :frown:
I just wanted to try to figure out if using this possibility I could avoid a few dozen revision manager cycles!</serie></percorso></percorso>

 

[Be_on_edge]

Thank you vespa,
In the meantime, I did some evidence. substantially the meaning of container/relative/absolute is what you say, except for relatives that it also works "to rise" if the number of levels to rise is the right one.
in practice, if in your example we had:
<percorso base="" di="" radice="">* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
and
<percorso base="" di="" radice="">♪<serie cartelle="" dentro="" di="" l'altra="" n="" una="">\file_b
with file_b pointing to file_a, the link continues to work even if you change the names of n folders, as long as they remain n (no more, or less)
clearly if you change the folder name1 no longer works.

moreover the container priority sequence --> relative -- absolute is the default of if in case the linkmgmt.txt has not been addressed in the file options/positions.

in many years of use of if I had never noticed of this relative pointing system.

Unfortunately several important changes to the structure of the archive are forced to do them and I am aware that it will be a workmanship. :frown:
I just wanted to try to figure out if using this possibility I could avoid a few dozen revision manager cycles!</serie></percorso></percorso>

before the dozen revision manager cycles I recommend you to use "redefined links" always accessible by revision manager.

in practice you work directly by renameing portions of the paths contained in the links of the files.
very fast to use.

Hi.

 

[ApeGana]

before the dozen revision manager cycles I recommend you to use "redefined links" always accessible by revision manager.

in practice you work directly by renameing portions of the paths contained in the links of the files.
very fast to use.

Hi.

Well, yes, I meant this:wink:
otherwise the cycles of revision managers would have been a dozen... of thousands!! !

cmq thanks. :finger: