I'm sure there is a program out there that could solve our problem. I think "My Briefcase" may have this option. When we load the library from our server it takes about 5 times longer to load than it would if it was on our local PC. How can we make sure that everyone is using the same library if we load it off our local PC. It would be perfect if we had a program that could update it every time we logged on the our local PCs because some people tend to forget to update!
Red wrote: How can we make sure that everyone is using the same library if we load it off our local PC. It would be perfect if we had a program that could update it every time we logged on the our local PCs because some people tend to forget to update!
There are several responses to your problem :
1. Synchronising directories :
There is an excellent utility called robocopy that can be to sync dirs, used in a command line batch that would be executed at each logon (put a link to the batch file in your startup dir)
download : http://www.devhood.com/tools/tool_details.aspx?tool_id=321
help : http://www.ss64.com/nt/robocopyXP.html
But you might also consider working differently :
2. Have you ever tried the satellite library option ?
Archicad will make a local copy of the library and only update parts that have changed...
Have a look at : http://download.graphisoft.com/ftp/publishing/ac_help/wwhelp/wwhimpl/api.htm?href=AC81_NewHelp-14-07.html
3. Organize your library differently :
a. Standards library (orginal one, 3rd party, etc) : nobody modifies it and everbody has a copy of these library on their own hard disk (ideally in the same path to avoid library loading problem : c:\common library\ArchiCAD 8.2 for exemple) -> as these libraries are never modified, they need to be copied only once and they are accessed locally
b. Custom library common for all projects -> on the network
c. Project specific library -> in the project folder
So only b. and c. library would have to be loaded from the network.
I personnaly use the third method, but might give a try at the 2nd one. I wouldn't do anything involving rsync at startup, because this involves too many adminsitration problems...