A co-worker and I recently started sharing enhancement tasks for an Access 2002 application. We quickly saw the benifits for having all the objects in VSS. (The set-up was painful, but we found the source control interface and used [Add database to Sourcesafe]. The checked out status saved us from stepping on each other's changes.)
The Micrsoft Source Code Control Whitepaper simply states
"When you add a secured database to source code control, the user and group permissions that existed are stripped away. You need to reapply your security settings after removing the database from source code control." That seems rather harsh but it is far.
We will import all the changed objects from the VSS project into an mdb outside of VSS. But manually applying the permisissions seems kind of tedious and easy to miss something. Is there a "good practice" or clever way to reapply the user and group permissions?
For example, a report from the mdb outside of VSS that shows the existing permissions applied to objects would help. But I'd love to hear of some way to import a VSS object into the outside mdb without first deleting the object in the outside mdb.
The Micrsoft Source Code Control Whitepaper simply states
"When you add a secured database to source code control, the user and group permissions that existed are stripped away. You need to reapply your security settings after removing the database from source code control." That seems rather harsh but it is far.
We will import all the changed objects from the VSS project into an mdb outside of VSS. But manually applying the permisissions seems kind of tedious and easy to miss something. Is there a "good practice" or clever way to reapply the user and group permissions?
For example, a report from the mdb outside of VSS that shows the existing permissions applied to objects would help. But I'd love to hear of some way to import a VSS object into the outside mdb without first deleting the object in the outside mdb.
