We have a relative small work group, and I am the main SW designer. Our network is quite crowded, and I notice a very large performance drop when working with files stored on the server compared to when they are local on my PC.
What I would like to do is have everything locally, and perform a copy to our server every day (or sync it when the file is not in use). The server keeps a backup of a large version history, so that is great for me. Having it on the server, also allows my co-workers to access the files. As I am the main user of the files, there is no issue with me having the latest version on my local drive, and an older version for my co-workers.
The issue I notice with this method, is that for some reason, SW has no clear way of how it references the file locations. Sometimes it uses a relative path (mostly when it goes deeper into the folder tree), sometimes it uses an absolute path.
When it uses absolute paths, it is impossible to open the files (without errors) from the server, as they have locations referenced to locations on my PC.
Is it possible to have SW save file location references (in assemblies etc) only in relative paths? I know that PDM could solve these issues, but it doesn't look like this will get implemented in our company.