Using Visual SourceSafe – Integrating VSS with Access 2007

This article is a part of SourceSafe / VSS Tutorial

With Access Source Code Control add-in, Visual SourceSafe can be integrated into MS Access to source control Access queries, forms, reports, macros, modules and data.

SourceSafe stores each Access objects as a text file. When you add an Access object to SourceSafe, Access exports the object to a text file in the working folder. Then the Access Source Code Control add-in adds the file to SourceSafe Database. When you check out/get an Access object from SourceSafe, the Access Source Code Control add-in copies the corresponding text file from SourceSafe to the working folder. Then Access imports the text file into MS Access database and turns the file into the appropriate Access object.

 

To integrate SourceSafe with Access 2007, please follow the steps below:

1. Install Access 2007 Developer Extensions, which includes source code control component. You can download it from: http://www.microsoft.com/downloads/details.aspx?familyid=d96a8358-ece4-4bee-a844-f81856dceb67&displaylang=en

2. Choose SourceSafe as the current SCC (Source Code Control) provider. For information on how to do it, see this: https://www.dynamsoft.com/codepool/microsoft-source-code-control-interface-msscci-registry-entries.html

3. Open the database in Access 2007.

4. Add the database into source control of SourceSafe. Click menu Source Control and click Add Database to SourceSafe button.

Add Access database to SourceSafe
(Add Access database to SourceSafe)

 

5. Then Access will prompt the following warning dialog box. Click Yes.

 

6. Log into a SourceSafe database and select the location to store the project.

Log in SourceSafe
(Log in SourceSafe)

 

Add the project to SourceSafe
(Add the project to SourceSafe)

 

7. Add the Access objects into SourceSafe.

Add Access objects into SourceSafe
(Add Access objects into SourceSafe)

 

8. Now the objects are in the source control of SourceSafe. You can find the SourceSafe functions by clicking the Source Control tab. You can also access some of the functions by right-clicking the items.

SourceSafe functions
(SourceSafe functions)

 

SourceAnywhere - the SQL Server-based SourceSafe Replacement The SQL Server-based Source Control Software Designed to be a SourceSafe Replacement SourceAnywhere for VSS - the Fastest SourceSafe Remote Access Tool Recommended by Microsoft The Fastest SourceSafe Remote Access Tool Recommeded by Microsoft

Links:
Previous article <<<<: Integrating SourceSafe / VSS with Visual Basic 6.0
Next article >>>>: Integrating SourceSafe / VSS with Access 2003
SourceSafe How To series home page: VSS / SourceSafe Tutorial

8 thoughts on “Using Visual SourceSafe – Integrating VSS with Access 2007

  1. Pingback: Source Safe?
  2. Do you have experience deploying the access mdb file after it has been checked into the vss? If you open the mdb file under another machine, ACCESS will throw all kind of msgbox at you, especially the fact that vss add-in may not be found on the current pc!.

    How does this help you?

    PSC0425

  3. How to set the working folder for MS Access application using this…?..When I set the working folder it shows only “.ACF” files.

  4. Some tips
    ———–
    If you have protection (=password) on the VBA part of the Access file, it is best to remove it. The VSS Add-in needs to access the VBA in order to export or import VBA modules and Forms and Reports modules. If the VBA is unaccessible it will fail and you will not be able to use VSS.

  5. Access 2010 and VSS 6.0
    —————————–
    The process of integrating VSS 6.0 with Access is very similar(identical?) to the process described in the post for VSS 2005.

    It works with VSS 6.0 (= origonal version), but people recomd to install VB6 SP 6. How can you tell if you have SP6 installed?
    After installing SP6 your VSS version is changed from 6.0 to 6.0d.

    How does Access export its objects to VSS
    ———————————————–
    All the tables are exported as one binary file called XXXX.ACB
    The ACB also includes hidden Access properties .
    Forms, reports, macros. modules are exported into text files, one file per object.
    The files are stored in a sub-directory called xxxx.scc. It is these files that are actually stored into VSS.

  6. Does VSS store the entire file as a binary MDB or does it store each form individually? Also how would I compile a database with all the different forms and reports and module?

    Kind Regards!

  7. After noticing I had to BUY VSS, I tried SourceAnywhere for Access 2007 source control. And I really like it. I wonder if that’s what all the banner ads were suggesting to me…. thanks.

Comments are closed.