Hi all,until now we have in our company been using a common .olb file for about 15 different schematic designers. We have had some problems with this. It seems like the write protect handling is not good enough so sometimes two users have been able to access it simultaneously which results in lost work etc.
Another problem is when closing a schematic design with the library opened in the library tab. Then this project will keep a link to the .olb file and then the user accidentally opens the library when opening the project at a later stage.
All these problems "forces" the designers to use their own local library.Then we end up with a mess in the library references in the design cache.
At our site all users har write access to the file. We have tried to limit the write access to only two users, but it seems like Orcad removes the restrictions when saving the lib.So in general it seems to be hard to make this work in a multiuser environment. So I would like to hear from other persons with the same setup. What are your experiences? What do you do to make the library access safe?Any thoughts around this issue wold be great to hear!Going over to CIS is not an option right now, but we are currently moving to Orcad 16.6. Would this change anything when it comes to this issue?Thanks!
OrCAD Capture has two categories of libraries, Project Libraries, added to the project manager window, are considered to be specific to that project and are opened and locked when the associated project is opened; and Global libraries, added through Place>Part, Add Library, these are not considered to be specific to the project are are therefore not locked when any associated projects are opened <- this is the library configuration that you need to share a common library, or libraries, between multiple users.
The library configuration has been this way since DSN file locking was introduced somewhen about the 10.x versions.
In reply to oldmouldy:
In reply to Cantstandya:
If a Global Library is opened for editing, it will be locked for writing by all other users but "all" users will be able to read the library. Otherwise this would "pretty much" cripple using Global libraries to any reasonable extent. There is a chance in this scenario that a user will be able to place an "outdated" part, CIS has an extended preference to check for this.
I don't think that it is possible for any version to save a modified OLB file back to a "read-only" location.