Managing a personal library of solidworks multiversion components

3D Design Library
1

Hi all

 

I ask my problem, I am a service provider in a mechanical design office and often have to work with different versions of solidworks (2017/2018/etc.) Only when a library is created, it is attached to the version used. This is not a problem for future versions but makes it unusable for older versions.

After thinking about it, I thought about making a library specific to each software version, but this implies a significant amount of standardization work if I want to take advantage of each addition and modification regardless of the version.

Otherwise, each addition and modification would have to be made on a fairly old version, but this implies paying attention to the conversion of the documents.

I would like to have your opinions and reflections if you have already asked yourself this problem (quite specific to my job however)

2

Hello

for my part, I would create my library in the oldest version I might work with and I would make the parts of it read-only; This will prevent any recording to another version.

5 Likes
3

Hello

 

As ac_cobra, I'll do the same and if a component asks for new functions not present in the old SW, then I save it in its new version

A+

4

As a study provider too, we also work with many versions of SW.
For libraries, we often use the client's library, in which case it's quickly settled.
For our personal library, we copy the files in the case, it's easier at the level of the paths during the take-away composition of delivery to the customer.

As a result, I only manage the versions of Sw for the proto files and possibly the welded construction profiles.

1 Like