VS2010, Access XP, & VSS 6.0b install

Question

 

Howdy all,

I'm setting up a new computer (Win7 x64) with Visual Studio 2010, Access XP & Office 2010.  (I'm the IT guy for this project)

Everything works fine until I try to install Visual Sourcesafe 6.0b (included in the Office XP professional set).  Without VSS, I can't open the code from my Access XP application.  When I try to install a warning pops up and tells me that "acmboot.exe" has a known conflict with Win7.  If I install it anyway, it seems to install but when I try and open my application in Access XP, it crashes with no warning and when I open an accdb in Access 2010 it tells me "Visual SourceSafe not installed" and then dosen't allow me to work with the code.

I've been searching for answers for a while now.  The same question was asked at (http://www.sevenforums.com/software/11867-visual-sourcesafe-win7.html)

Tim Anderson addresses a similar question regarding Vista & Visual Studio at http://www.itwriting.com/blog/?p=167 but I don't know enough to tell if this is the same issue.

I've never worked with or installed VS before so I don't know if my problem is connected to VS2010 installation.

I guessing at:
•UAC problems
•32 vs 64 bit conflicts
•DLL overwrites
•Gremlins

I'd really appreciate any and all help.  I really don't want to have to have people working off of 2 diff machines.

Thank you for your time,

Joe

--

 

Could this hotfix do the trick?  http://archive.msdn.microsoft.com/KB976375

It is supposed to allow existing SourceSafe customers to use SourceSafe with Studio 2010.  So if I don't install VSS6 and just install VS2010 and the hotfix would that allow me to open my Access projects?

/Joe

Answer 1

http://www.microsoft.com/Windows/compatibility/windows-7/en-us/Details.aspx?type=Software&p=Microsoft%20Office%20XP%20Small%20Business&v=Microsoft&uid=10&l=en&pf=2&pi=1&c=Business%20%26%20Home%20Office&sc=Office%20Suites&os=64-bit

Looks like a compatibility issue between Office XP and Win 7 x64.

Answer 2

Hi Model_m,

The hotfix just works with VSS 2005, not for VSS 6.0.

And as pvdg42 said, please try to refer the compatibility issue between Office XP and Win 7 x64. I think I could recommend you to dowanload the VSS 2005 and the upgrade for Office XP from MSDN subcriber download site: http://msdn.microsoft.com/en-gb/subscriptions/cc137115.aspx

By the way, please try to trefer to this article to know how to work VSS 2005 with Access 2007 and later version: http://www.kevingao.net/sourcesafe/integrating-sourcesafe-vss-with-access-2007.html For Access 2010, please download the Microsoft Access 2010 Source Code Control from http://www.microsoft.com/download/en/details.aspx?id=6840  

 

Sincerely,

---

Bob Bao [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 3

The VSS error message poped up also in A2010s so I don't think it's a conflict with XP

We don't actually use sourcesafe as a versioning software. the only reason we install it is because it gives us error messages otherwise. We are a small shop and until recently ony had one programmer. Maybe there is a way to avoid VSS entierly?

/Joe

Answer 4

VSS 6.0 is old, and Acess 2010 can work with VSS 2005.

And start from Visual Studio 2008, Team foundation Server including the source control tool to replace the VSS, so now VS 2010, it uses TFS source control.

Sincerely,

---

Bob Bao [MSFT]
MSDN Community Support | Feedback to us
Get or Request Code Sample from Microsoft
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Answer 5

Hey folks,

In the end the lesson learnt from this story was don't install more than you need.

When I walked through the setup of a clean machine step by step I found that I could do 99% of what I need without the developer & VSS install. As such I just installed the main Access XP element (after installing 2010 as Saberman pointed out above) and it all works nicely. In the event that we need the XP developer/packaging elments, I left one older XP machine on the network with a full install of Access XP & dev stuff. Hopefully over the next 2 months we'll be completely off of Access XP.

Did we solve the problem? No. Did we avoid the problem? Yes. And given that we phasing out Access that's ok. I am a little sad that I didn't solve the problem and learn new stuff but...

Thank you all for the help,

Joe