file path together

[Pablo]

the path where you stored the assemblies that can be the network when you work on the network or the local one when you work locally. in this way you guarantee the operation.

That's right. but in this way I should always change the order of priority in setting "file placements > pre-document position"?? I did the necessary tests and I still have to use a manual system to make sure that sw goes fishing where I want, and not where he wants.. .
by giving the local network priority > I told myself: not finding the sw network goes to search locally, ok, but if I am in the office (connected to the network) and decide to work locally (e.g. for greater speed) I have to remember or to disconnect the network or to reverse the order in the setting, otherwise.... down salads of paths!
I would like to find a "switch" (like a macro) that would make this "inversion" of sectations without too much dismantling. .

 

[re_solidworks]

the flavio solution (which I greet) is in my opinion the best and the cleanest. I also adopt the same system with the difference that when in the office I use the net use command that connects a network disk, instead of subst that creates a virtual disk.

in the bat files that I created disconnect all disks (virtual and network) and then I execute the connections I need. In this way I can switch disks in a moment and without rebooting the pc.

my bats also have some extra rows because I also use them to switch session and order:

disconnect all discs
connect the necessary disks
I follow a change of system logs for pdm
start solidworks

This prevents me many errors even from my collaborators not too hard on network virtual disks and system logs.

to synchronize use the xcopy command of windows with /d/f/s/y options and always worked wonder.

 

[Pablo]

the flavio solution (which I greet) is in my opinion the best and the cleanest. I also adopt the same system with the difference that when in the office I use the net use command that connects a network disk, instead of subst that creates a virtual disk.

in the bat files that I created disconnect all disks (virtual and network) and then I execute the connections I need. In this way I can switch disks in a moment and without rebooting the pc.

my bats also have some extra rows because I also use them to switch session and order:

disconnect all discs
connect the necessary disks
I follow a change of system logs for pdm
start solidworks

This prevents me many errors even from my collaborators not too hard on network virtual disks and system logs.

to synchronize use the xcopy command of windows with /d/f/s/y options and always worked wonder.

If I understood correctly: on the laptop I should connect a network drive by assigning to the drive the folder of my archive? but I'm sure that when the receipt (I see that physically the folder continues to exist on the disk) sw does not go fishing from there anyway?
or should I create a virtual disk real and purple? What I've never done, honestly.... is it very complicated? thanks x the help:smile:

 

[re_solidworks]

If I understood correctly: on the laptop I should connect a network drive by assigning to the drive the folder of my archive? but I'm sure that when the receipt (I see that physically the folder continues to exist on the disk) sw does not go fishing from there anyway?
or should I create a virtual disk real and purple? What I've never done, honestly.... is it very complicated? thanks x the help:smile:

Consider that swx is a little stupid in this, so if you have the drawings in the z disk:\draws to him does not care what is z, the important thing is that it exists.

with these files you connect z to the network when you are in office as a network drive and a laptop folder when you leave.

I never work with the laptop in the office, but I ready it on the docking as a "mulet" in case one of the workstations create problems. before exiting I follow a data sync with xcopy, to return to the example above the string will be:

xcopy \\server\dati\disegni d:\dati\disegni /d/f/s/y

this string should be inserted into a text file saved with the Bat extension and will copy all new or modified files after comparison between server and laptop. It's the quickest thing because he works in dos and has no gingilli. it is not a true synchronization because you will find all the new files but this command does not erase from the destination what is no longer on the origin. what I do sometimes is shave to 0 l laptop and run xcopy from head.

If you need to connect to the network you will have a bat called "network disks.bat" in which you will write:

subst z: /d
net use z: \\server\dati\disegni

if you have to work locally you will have another bat file that will be called "local disks.bat" which will have as syntax:

net use z: /delete
subst z: d:\dati\disegni

the net use command connects and disconnects network disks, the subst command creates and deletes virtual disks.

 

[lelepanz]

Thank you.
I was also having the same problem that when I work locally for greater speed and then synctoy with synctoy, then I go fishing from the server the particoalri.
I brutally add one to the directory on the server, so that then sw fishes from local files. finished the day, I take off the a, synchronize and away....
Now I'll try the smartest ideas. :

 

[Pablo]

Consider that swx is a little stupid in this, so if you have the drawings in the z disk:\draws to him does not care what is z, the important thing is that it exists.

with these files you connect z to the network when you are in office as a network drive and a laptop folder when you leave.

I never work with the laptop in the office, but I ready it on the docking as a "mulet" in case one of the workstations create problems. before exiting I follow a data sync with xcopy, to return to the example above the string will be:

xcopy \\server\dati\disegni d:\dati\disegni /d/f/s/y

this string should be inserted into a text file saved with the Bat extension and will copy all new or modified files after comparison between server and laptop. It's the quickest thing because he works in dos and has no gingilli. it is not a true synchronization because you will find all the new files but this command does not erase from the destination what is no longer on the origin. what I do sometimes is shave to 0 l laptop and run xcopy from head.

If you need to connect to the network you will have a bat called "network disks.bat" in which you will write:

subst z: /d
net use z: \\server\dati\disegni

if you have to work locally you will have another bat file that will be called "local disks.bat" which will have as syntax:

net use z: /delete
subst z: d:\dati\disegni

the net use command connects and disconnects network disks, the subst command creates and deletes virtual disks.

thanks for the eloquent explanation, king, and I also thank flavio that in recent days had already routed me on qs. via.
As soon as I have a little time, I'll get the evidence of the case and tell you.

 

[re_solidworks]

I've been doing this for three years and I've had no problem.

 

[gianniturbina]

the most correct solution is to set in sw options, file locations, default document location, the location where you stored the axioms that can be networked when you work on the network or local when you work locally. in this way you guarantee the operation.

Good morning to all;
I have a similar problem on my station;
I have the search paths set up on directors who actually do not exist or that I do not care;
I have tried several times to delete them (from options/file position) but reappeared automatically.
How do you eliminate them?