DBLib and SVNDBLib Libraries

SVNDBLib requires that each *.Schlib file only have one symbol. This is required for version control of the symbol files.

DBLib libraries can have multiple symbols in one *.Schlib file.  However, the best practice is one symbol per file.

Ideally the Library Ref and Filename are the same, for example:

Library Ref = RESISTOR
Library Filename = RESISTOR.SCHLIB

If the Library Ref and Filename are matched and saved in a single folder you can be sure that no duplicate Library Refs exists in your library.

Single part files will reduce conflicts in multi-user database library environments.  

Imagine a DBLIB with a few hundred symbols in one *.Schlib file.  If two different users open a large multi-part DBLIB file and they both add new parts, what's going to happen ?  

When last user saves the multi-symbol *.Schlib file they will overwrite the work done by the first user that closed the file before the second user.  This same logic applies to *.PCBLib files.

If you have one symbol per file it's simple to migrate from DBLib to SVNDBLib if you later decide to go with SVNDBLib.

Migrating to SVNDBLIB is simple once you know how to set up a repository and use SVN. 

Consider the users in your design group. Are they comfortable with using SVN ?  

Some training may be needed if users are new to using SVN.

My advice for users that are setting up their first database library is to start with DBLib.

If have any questions about database libraries you can reach me at: Contact Parts 

That's it !