At work we operate using a shared Toolbox location forSolidWorks and have done so for some years. This works finegenerally, however as the company has grown we have started to givestandard fixings (nuts, bolts & washers etc) an internalreference part number - every different type of bolt gets a partnumber.
We do not use configurations for parts and our part number and BOMsetup works using the SolidWorks file name. As a result we have tosave a copy of the toolbox item and give it a unique number (inaccordance with stock control procedures) and stripping out anyconfiguration history it might have.
I thought that this technique would work well - we don't spend timemodeling standard parts already provided by SolidWorks. But twothings are slight problems:
1. The copied toolbox item (save as / save as copy) retains'knowledge of having come from the tool box.
2. I think that on occasions this is causing a toolbox and toolbox configuration error messages? Especially if one toolbox item isreplaced for another
Any ideas?SolidworksToolbox
We do not use configurations for parts and our part number and BOMsetup works using the SolidWorks file name. As a result we have tosave a copy of the toolbox item and give it a unique number (inaccordance with stock control procedures) and stripping out anyconfiguration history it might have.
I thought that this technique would work well - we don't spend timemodeling standard parts already provided by SolidWorks. But twothings are slight problems:
1. The copied toolbox item (save as / save as copy) retains'knowledge of having come from the tool box.
2. I think that on occasions this is causing a toolbox and toolbox configuration error messages? Especially if one toolbox item isreplaced for another
Any ideas?SolidworksToolbox
