Using Visual SourceSafe: An Overview
When you want to place a database under SourceSafe control, you create it from a SourceSafe project; this database becomes the master copy. Each developer works on a local copy of the database, and no one can modify objects in the database until the developer checks them out. When a developer checks out an object, Visual SourceSafe copies it into the local database. No other developers see changes made to the object until the developer checks it back in. When the developer checks the object back in, Visual SourceSafe copies it from the local database to the Visual SourceSafe project.
With the exception of modules, only one person can check out an object at a time. This means that two people can't make changes ...
Get Alison Balter's Mastering Access 2002 Enterprise Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
