Does anyone have any suggestions on how to have a network toolbox that client computers direct to instead of the toolbox on the client computer?
Thanks for the help.
Change your settings at Tools > Options > System Options > Hole Wizard/Toolbox
In the help file:
You can do this, but you ahve to path it in the toolbox.ini file as well as
in tools>options>toolbox/holewizard path.
Where can i find the "toolbox.ini" file?
Before implementing in your system check functionality and speed. Toolbox is an "configurator" and worked (very) slow on the 1Gb network, at my work.
After a crash which made the .mbd file, which feeds the toolbox data, corrupt we decided to use the design library with predefined parts, some with design table, only.
We do not use PDM. Design library behaves reliable.
If there is someone with better ideas let me know please.
As Troy pointed out, the help file is a great resource for setting up Toolbox.
If you have issues with speed over your network, it may help to do what I've done at my company. I set up a server based Toolbox file location but have all of the client computers run a batch file that copies the server install down to their own machine and they run it from there. I, as admin, manage the server install and update files as needed. When the users start up the .exe (I converted the batch file to an .exe), it looks at the server files and compares them to the local install and updates locally as needed. Typical file update time is seconds and this happens maybe once a week. This has been working very well for us for the past 9 months or so. This method has literally cut our access times in half when using 64-bit machines over a network. I converted the batch file into an .exe so the users can't mess with it and I only give them the shortcut to the .exe so I can update the .exe as needed and the users are blind to it.
The following is my batch:
@echo OFFREM This batch file is designed to copy any file from the server that is newer than the local versionREM by doing this and changing the SolidWorks system option to use a local copy of the Toolbox/Hole Wizard,REM the user should have improved access times for hardware and hole wizard holes compared to having a serverREM based Toolbox/Hole Wizard location.
================================================================REM Set the title for the command window
TITLE SolidWorks Start-up Routine
REM /D = Copies only those files whose source time is newer than the destination timeREM /E = Copies directories and subdirectories, including empty onesREM /H = Copies hidden and system filesREM /I = If destination does not exist and copying more than one file, assumes that destination must be a directoryREM /K = Copies attributes. Normal Xcopy will reset read-only attributesREM /R = Overwrites read-only filesREM /Y = Suppresses prompting to confirm that you want to overwrite an existing destination file
ECHO Toolbox comparison in progress. Please wait...if EXIST "C:\solidworks data\toolbox" (XCOPY "\\guinness\swcommon\sw_toolbox\*" "C:\solidworks data\toolbox" /D /E /H /I /K /R /Y)if NOT EXIST "C:\solidworks data\toolbox" (XCOPY "\\guinness\swcommon\sw_toolbox\*" "C:\solidworks data\toolbox" /E /H /I /K /R /Y)CLSECHO Local Toolbox has been sync'd. Starting SolidWorks in...3 secondsTIMEOUT /T 1 > nulCLSECHO Local Toolbox has been sync'd. Starting SolidWorks in...2 secondsTIMEOUT /T 1 > nulCLSECHO Local Toolbox has been sync'd. Starting SolidWorks in...1 secondTIMEOUT /T 1 > nul
REM The following will launch SolidWorks from the local installation directory using swspmanager.exeREM swspmanager.exe will compare the current installation of SolidWorks to the folder on the server REM with the same share name and if it sees a new service pack it will force an upgrade
START /d "C:\Program Files\SolidWorks Corp\SolidWorks" swspmanager.exe
Is the \\guinness\... the network location of your toolbox?
Is that the only thing I would need to change to use this batch file?
Retrieving data ...