Search: Advanced search
Please enter a keyword or ID
Surround SCM Microsoft Access Integration
Surround SCM supports integration with Microsoft Access. See Surround SCM Third-Party Integrations for supported platforms and versions.
The following article includes information about installing the integration components, configuring the Surround SCM connection, adding Access databases to Surround SCM, performing Surround SCM actions, and integration restrictions, caveats, and troubleshooting.
The Microsoft Office plug-in is optionally installed during the Surround SCM Client installation. If you did not install it initially, rerun the client installer.
You must also install the Access source code control add-in to enable communication with Surround SCM.
When you start Microsoft Access, the Surround SCM Server address, port, username and password are retrieved from the registry. If the connection is not successful or you want to switch to another server you can manually configure the connection.
When you add a project to Surround SCM from Access, all objects in the project are divided into separate files that can be independently controlled. The files are added to a subrepository created in Surround SCM with the same name as the project file appended with an .scc extension. Access requires a two-level relationship between a project file (.mdb) and a project directory (.scc) because any files in the project directory are recognized as part of the project. If a project file is stored in its own project directory, Access cannot open it.
To add an Access database:
You can access the following Surround SCM commands from the Source Control menu or tab in Access: Add, Check In, Check Out, Differences, Get, History, Properties, Share, and Undo Check Out.
Adding objects to Surround SCM
You can add Access objects to Surround SCM.
Getting the latest version of objects
Get the latest version of an object when you want to update your local copy but do not need to make any changes.
Checking out objects
Check out objects when you need to modify them.
Undoing check out
If you modify a checked out object but decide you do not want to save the changes, you can undo the check out. This discards any changes made to the object and checks in the file to the server.
Checking in objects
Check in objects with changes to remove the lock on the files and make the changes available to other users.
Viewing file history
You can view a source file's history and work with historical file versions.
Viewing file properties
You can view Surround SCM file properties from Access.
Viewing file differences
You can diff files to compare, accept, or reject differences between two file versions.
Creating databases from Surround SCM
To create a database from a project already stored in Surround SCM, choose Source Control > Create database from Surround SCM. You must select the repository with the .scc extension for the project you want to open. If the database is under source control, the project is retrieved and used to create a new single project file in the parent directory of the local .scc project directory.
Access requires the local project directory used as the working directory to have the same name as the project repository in Surround SCM including the .scc extension. When databases are added to Surround SCM, the project repository is automatically created with the correct naming format and should not be modified.
The Microsoft Office plug-in uses the MSSCCI API for source code control integration. To avoid potential data corruption, Access project files under source control should not be modified outside of Access if the project is in use by other users.
If you encounter problems viewing the check out status of Access files stored in Surround SCM, reset your working directory.