Apparently there is no SS integration for access 2003. Which makes access
2003 no use whatsoever if you have a programming team geater than one,
considering access wrecks itself if more than one person uses it at the same
time.
See microsoft.public.access.devtoolkits for more info.
Is there really no VSS integration available for Access
2003??? It seems to me that zero effort is required to
maintain VSS compatibility since the database formats
have not changed! Where was this PROMINENTLY stated in
the documentation??? How are we supposed to perform
significant multi-user development tasks without it?
If this is truly the case, Microsoft needs to publish a
list that includes items they have dropped as prominently
as items they have added so I can determine whether or
not I want to upgrade (and have my organization purchase
upgrades as well).
As is the case with most groups, we have found the recent
versions to Office to offer meaningless new capabilities
(which why so few organizations purchase upgrades).
However, what is significant is the useful features that
have been eliminated!!!
Moving to Access 2003 should be called a downgrade not an
upgrade if VSS integration is no longer available.
>-----Original Message-----
>Apparently there is no SS integration for access 2003. Which makes access
[quoted text clipped - 31 lines]
>
>.
Kevin Yu [MSFT] - 23 Dec 2003 10:24 GMT
Hi Michael,
I've done some research and found that Access 2003 doesn't work currently
with VSS. However, a new version of the add-in (accscc10.dll) that will
work with Access 2003 and VSS 6.0d is in works. It will be published on the
web site for download when it will be ready.
Kevin Yu

Signature
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
David Adams - 26 Dec 2003 15:39 GMT
This is unreal. We have been messing with this for the
last two weeks and I can not belive that I have to go to a
news group to find out it does not work with source safe.
Why don't they post it, I have been looking for this for
the last week. It would have saved me a ton of
development time. Now I have to uninstall Office 2003 on
4 development computers untill this is fixed. I don't
think Microsoft will take a return on the product.
>-----Original Message-----
>Hi Michael,
[quoted text clipped - 10 lines]
>
>.
Paul Shapiro - 27 Dec 2003 12:53 GMT
In a quick test, I was able to install the XP developer on a system with
Access 2003 and get the sourcesafe integration to work. I didn't do any work
other than a quick test, but you might try it.
Paul Shapiro
> This is unreal. We have been messing with this for the
> last two weeks and I can not belive that I have to go to a
[quoted text clipped - 16 lines]
> >
> >Kevin Yu
Kevin Yu [MSFT] - 31 Dec 2003 02:37 GMT
Hi Paul,
It's very possible that installing the old source safe add-in will work for
access 2003 but I want to reiterate that is not a currently supported
scenario with Access 2003. Please wait for the official supported way to
get VSS to work with Access 2003.
Kevin Yu

Signature
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."