I have installed Vault Server & Client 4.0.6.15954 on my WinXP SP2 PC. I have Office 2003 installed as well. Can use Vault with Access 2003?
Will it require using the Access 2003 Source Code Add-In: http://www.microsoft.com/downloads/deta ... laylang=en
and a tool like CVS SCC Proxy: http://www.pushok.com/soft_cvs.php ?
Microsoft Office 2003
Moderator: SourceGear
We don't support the integration with Microsoft Access. You can use Vault to check in and out any kind of file without using the integration. I think some customers use it integrated anyway, but that's an 'at your own risk' thing. We haven't tested with Access. The integration we support is listed in our IDE Integration Overview article.
If other customers are using it with Access, could you tell us your experience with it here?
If other customers are using it with Access, could you tell us your experience with it here?
Vault and Integrated Access Projects
I have, with some degree of success and relatively little difficulty been able to use Vault in conjunction with integrated Access 2000 projects under 3.5. However initial testing wth 4 has proven fruitless. I have yet to be able to get Access to spawn Vault from inside the IDE and found this post while farming the group for help.
In order to get it to work at all you will need to at least install the developer extensions for Access to enable the source control integration. But as I stated, it still might not work with 4.
I understand Sourcegear doesn't support this configuration, but it would be greatly appreciated if anyone could point those of us who, for good or bad, use Access for development and want to employ a source control system superior to Sourcesafe to any information or other posts available.
In order to get it to work at all you will need to at least install the developer extensions for Access to enable the source control integration. But as I stated, it still might not work with 4.
I understand Sourcegear doesn't support this configuration, but it would be greatly appreciated if anyone could point those of us who, for good or bad, use Access for development and want to employ a source control system superior to Sourcesafe to any information or other posts available.
Vault and Integrated Access Projects
To follow up on my last post, I have been successful in getting both Access 2000 and 2003 and Vault to work together at the very least on a shallow level.
My test setup was windows 2000 with SQL 2005 running in Virtual PC 2007. Both the vault client and server are 4.1.0.16216. The Access projects were imported from SourceSafe with the import tool.
All of the functionality I tried appears normal. Opening a project from source control, check out, check in, and undo check out all functioned. And on top of that Vault doesn't care that it's an integrated project!
Now if I can just find a way to automate the get latest...
My test setup was windows 2000 with SQL 2005 running in Virtual PC 2007. Both the vault client and server are 4.1.0.16216. The Access projects were imported from SourceSafe with the import tool.
All of the functionality I tried appears normal. Opening a project from source control, check out, check in, and undo check out all functioned. And on top of that Vault doesn't care that it's an integrated project!
Now if I can just find a way to automate the get latest...
You could use the command line client for the Get Latest, put it in a .bat file, and then you can schedule the .bat file to run at a particular time.Now if I can just find a way to automate the get latest...
I can see if I can track them down, but it could take a while.I understand Sourcegear doesn't support this configuration, but it would be greatly appreciated if anyone could point those of us who, for good or bad, use Access for development and want to employ a source control system superior to Sourcesafe to any information or other posts available.
I very much appreciate your assistance on consolidating this information.
Source control integration in Access is a bit of a difference beast. Getting latest can be done with the Vault Command line Client, but Access then also needs to import the newly downloaded items into the database on the client machine. This appears to work the same with Vault in place of Sourcesafe, but automating the whole process is proving challenging.
Source control integration in Access is a bit of a difference beast. Getting latest can be done with the Vault Command line Client, but Access then also needs to import the newly downloaded items into the database on the client machine. This appears to work the same with Vault in place of Sourcesafe, but automating the whole process is proving challenging.