No Source Control in Access 2003

Geek8 Comments

I have been thinking about migrating my Microsoft Access runtime applications to the latest version of Access to be more up to date. Access 97 has been a solid workhorse for many years but things come up now and then it can’t deal with them.

So I installed Office 2003 and the Visual Studio Tools for Office (VSTO) and to my surprise I couldn’t figure out how to use the source control features that used to be there in previous versions. I found the toolbar, but everything was disabled. If you are developing Access solutions, this is a must have feature! I checked all over the Internet but found nothing.

I contacted Microsoft Support and found out the answer I didn’t want to hear — they dropped the support! They informed me that reason is that VSTO is based on Visual Studio IDE, so the SourceSafe integration was largely dropped from Office (since Visual Studio handles it). Of course, this doesn’t work for Access that doesn’t have managed code (just VBA), but without the addin for other Office apps they felt there wasn’t enough dev resources to keep it alive. Suck.

So all of us Access dudes are out of luck? Apparently not. The add-in that came with Microsoft Office Developer XP, which is no longer shipping for 2003, will save the day. If you have this, you can take the add-in from that package and register it on your system (it is a COM addin and only needs to be registered with regsvr32). I found this on my Microsoft CD in the Productivity Tools directory. I copied this whole directory to my machine and then registered the file ACCSCC10.DLL. I fired up a DB and the source control menu is back!

Microsoft plans to document this at http://support.microsoft.com/?id=828089

I have been burnt by Microsoft many times. That was too close to the flame again.

  • Stephan

    I have tried this valuable advice, but the only result was that only the “Run Source Safe” button is enabled.

    The question is, how do I enable the rest of the buttons?

  • http://brandon.fuller.name/ Brandon Fuller

    Not sure. Mine are all enabled.

  • http://www.squarewavecorp.com steve

    Our company has created a similiar

    VBA source control add-in; the difference

    is that our add-in works with ANY VBA

    Host (not just MS Office Apps).

    The product is very new and we are

    looking for “reviewers” for our

    Source Control for Applications.

    drop me a line at sascorp@adelphia.net if

    interested.

    sas@squarewavecorp.com

  • Rick

    I get the same result as Stephan. Any ideas, anybody? I was really hopeful when I stumbled across Brandon’s idea.

  • http://brandon.fuller.name/ Brandon Fuller

    Rick, it all works just fine for me. Not sure what was going on in Stephan’s case. My guess is that he didn’t add his database to source control.

  • Rick

    SourceSafe addin works now! I don’t know what changed — maybe I had Access open at the time, or had to reboot. Anyway, thank you very much! This will be a great help!

  • Andrew Cherry

    Just in case anyone is still struggling with this in Access 2003, this is what you’re looking for…

    http://www.microsoft.com/downloads/details.aspx?familyid=2ea45ff4-a916-48c5-8f84-44b91fa774bc&displaylang=en

  • Keith Safford

    Yes, the VSS add-in works, however, when you create an MS Access DB that was added to VSS in Access 2003 format, it comes out as Access 2000 format. Sooo, if you add functionality that is Access 2003, what happens to it when you create database from source safe project.