With the recent discussion that included libraries, updating them and old 
designs etc as part of it, I thought I'd ask a few questions separately to 
that.

Here we usually have a library for each design database, this means each 
design is totally separate, there is no worry about updating components in 
a new design affecting the old, as their libraries are totally separate. 
BUT, this does mean a LOT of tedious copying across commonly used 
components between libraries when creating a new design.

So, me and my colleague (only two Protel users here) wondered about 
creating a central library for all our designs. This sounds better, 
however I can find flaws in this also, such as when you require a custom 
footprint due to a particular layout for only one single design and also 
how to control the library for access, also us both ending up adding 
components in duplicate!

I'm interested to find out how everyone else has their libraries set up 
and how it all works, pro's and con's etc. 

I also need to know how to set it up, will I need a separate ddb 
containing just libraries or just library files to import into each 
design? Either way I also need to maintain integrity of the library in the 
case a ddb goes corrupt aswell, as if all the components/footprints are 
only in the central library and it gets corrupted, I'm in for a lot of 
work!

Thanks,

Best Regards

Norman Webster

Development Engineer
Gas Detection Systems
--------------------------------------------------------------
Draeger Safety UK Limited
[EMAIL PROTECTED]
www.draeger-safety.com
---------------------------------------------------------------
Draeger Safety >> Pioneering Solutions
 
____________________________________________________________
You are subscribed to the PEDA discussion forum

To Post messages:
mailto:[email protected]

Unsubscribe and Other Options:
http://techservinc.com/mailman/listinfo/peda_techservinc.com

Browse or Search Old Archives (2001-2004):
http://www.mail-archive.com/[email protected]
 
Browse or Search Current Archives (2004-Current):
http://www.mail-archive.com/[email protected]

Reply via email to