We are about to setup source control for the first time, and the majority of our development is in MS Access (2002). Will VSS 2005 work with the Access add-in for VSS? I would like to give it a try if it's possible. Otherwise, we have to go with the current VSS which isn't so friendly for developers working at remote locations.
Thanks,
-Tom
Thanks for the reply.
I'm glad to hear you're optimistic about the Access add-in still working with VSS 2005. I hopefully will be trying it out in a couple weeks once we get a server setup. My impression is that VSS 2005 is a significant improvement over the prior version in more ways than just remote development, so it will be good if we can get this going. However, not being able to use the remote access option is quite unfortunate (not that I expected it... source control in Access isn't high on anybody's list).
My question is this: if remote access to a VSS 2005 is only available in the Visual Studio .Net 2005 IDE, that sounds like it's not an available feature for any other development tool, yes? That would seem to limit the appeal of VSS 2005 quite a bit if it's true.
Regards,
-Tom
Remote access to VSS2005 should be available to any provider supporting MSSCCI interface (e.g. VC6, VS2003). Someone wanting to use this combination will have to use a 3rd party tool to switch the active MSSCCI provider (or manually change the registry).
I may be wrong, but as far as I know, Access2002 doesn't use MSSCCI interface, so I don't think Remote Access will be available for it.
Alin
You write "...as far as I know, Access2002 doesn't use MSSCCI interface, so I don't think Remote Access will be available for it." Wouldn't it be nice if it did? Couldn't you talk to some of the folks over in the Access group and mention this? It seems the Access add-in should be able to be coded to the MSSCCI interface without too much headache, yes?
I know, not much hope... but hopefully it doesn't hurt to ask.
Regards,
-Tom
I sent your feedback to someone in Access team that worked last time on the scc plugin.
I have no idea what are their plans for the next version and whether they will consider using MSSCCI, but note that depending on what feature they want to have in their scc integration plugin, using MSSCCI may not be appropriate (for instance, msscci does not support getting specific versions, getting by label, etc)
Alin
This may be beside the point, but I have now upgraded my VSS from v6.0 to 8.0 and re-installed the MS Access v6.0 VSS integration add-in. Afaik there is no updated plug-in.
Things sort of seems to work, but the check-out status of the items inside Access is not correct and subsequently I am not allowed to save any changes to the project. So unless I am able to solve that, my conclusion is that the integration with VSS 2005 does not seem to be ok.
Have you folks continued to have success with VSS 2005 and Access 2003? We were using the previous version of VSS with Access 2003 for a year or more with out too much trouble. But since we got the new version of VSS up and running, it's been a constant struggle--items marked with different checkout statuses, multiple database name files (though I can't really find any information on what that means, or how to prevent it). I'm in the midst of trying to convince my team to roll back to the older version of VSS, but I'm not really sure that's the right direction.
Anyone else have positive or negative experiences with this combination of tools.
We have a very large Access database, with a lot of linked tables that we programatically drop & link, and we find that we need to open the database with all the tables dropped or else sourcesafe makes us WAIT for minutes to get in.
We also have issues when creating objects in this large database. Once a developer has done that, the hookup to sourcesafe gets pretty darn slow. Recreating the database solves it.
It's definitely a good idea when checking in your "data & misc objects" object to make sure your Access database is decompiled & compacted.
We've definitely seen the multiple database name files thing... when it comes up, we deal with it by using sourcesafe's tool to clear out our temp directory and then rebuilding our Access database from sourcesafe.
I hope that helps. I would stay with VSS 2005 if you can... from my reading, it seems that everybody hates the earlier versions.
Regards,
-Tom
