VSS VBA Integration in Office 2000 problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

MalsNews - 17 Sep 2003 01:56 GMT

I'm using Office Developer 2000. I want to create Access database as
part of VS project, which is under Visual Source Safe control. I have
the problem if I create the database in Access 2000, and I select
Tools/SourceSafe/Add database to ..., it creates the project branch in
VSS, but does not add anything in source safe, but it creates .scc
folder in the folder where the .mdb file is stored. This .scc folder
is also empty.
I have re-installed Office200 developer to ensute VSS integration is
installed. The PC is a Windows Terminal Server 2000 running Citrix
Server and has Visual Studio .Net 2003 installed. Office is service
packed to SP3 and Windows 2000 Server has been service packed to SP4.
All current Windows update patches have been installed up to date.
VSS is installed with VS.NET and is V6.0d.
This was not a problem on the previous system up to a few weeks ago
which was running the previous version of .Net, did not have up to the
very latest Windows Update patches and was Win2K sp3.
Cheers

Reply to this Message

Nicholas P. Nelson - 24 Sep 2003 20:11 GMT

There has been some talk of issues like this in the various newsgroups, but
I've seen no answers as of yet.

My setup is Office XP/ VSS 6.0d (it seems that the culprit is 6.0d). I
experience the same symptoms as you. It seems like the Sourcesafe guys are
pointing the fingers at the Access guys since Access "owns/deploys" the
integration dll. I haven't seen any replies from the Access group yet
though.

I suspect that the problem is reproducible using the following steps.

1) Start with a fresh Windows machine (Windows XP in my case)
2) Install Office XP
3) Install SourceSafe 6.0c (I don't know if a fresh install of 6.0d would
reproduce the problem)
4) Install the Access SourceSafe add in
5) Install all patches (Windows and Office)
6) Install VS.NET 2003 (making sure you install Sourcesafe 6.0d)

At this point, you should experience the symptoms described. I would be
happy to provide more details if needed.

Can someone from Microsoft help us out on this one?

> I'm using Office Developer 2000. I want to create Access database as
> part of VS project, which is under Visual Source Safe control. I have
[quoted text clipped - 13 lines]
> very latest Windows Update patches and was Win2K sp3.
> Cheers

Reply to this Message

MalsNews - 30 Sep 2003 03:47 GMT

To all VSS V6.0d integration users experiencing this problem. I have
solved it.

I contacted Microsoft Support here and got through to the professional
products support team and registered a support incident. The support
person directed me to this knowledgebase article which has been
recently added:

Microsoft Support for VSS6.0d integration problem
See http://support.microsoft.com/default.aspx?scid=kb;en-us;822845

I was informed that a hotfix would be supplied which indeed it was,
within 4 hours.

the hotfix supplied was:
Q822845_ENU_i386_MID143698_.zip

As we still had the de-commissioned development server with the
previous version of VS.Net, Access2000 and VSS6.0c in a working state
we were able to upgrade it to the current VS.Net - VSS6.0d and exhibit
the problem described by 822845 as was being experienced on our newly
commissioned development server. We then tested the hotfix on that
machine and verified that it indeed worked and induced no other
problems in VSS, Vs.Net or VSS integration. Having tested it we have
now applied it to our main development server where it is operating
successfully.

You will need to contact microsoft directly to obtain the hotfix.

Cheers
malsnews.

> There has been some talk of issues like this in the various newsgroups, but
> I've seen no answers as of yet.
[quoted text clipped - 37 lines]
> > very latest Windows Update patches and was Win2K sp3.
> > Cheers

Reply to this Message