[AccessD] VSS misbehaving

Steve Capistrant scapistrant at symphonyinfo.com
Thu Oct 27 10:10:07 CDT 2005


We're having a growing number of problems using Visual Source Safe.
Used with Access over the years, it presents occasional problems, not
terrible.  But our problems have amplified since applying it to .NET
projects.

1.  When one user creates a new object and checks it in, other users
can't see it (after attempting to Get Latest Version).  Yet the object
is clearly seen in the Source Safe project itself.  

2. Adding or deleting an object to a VB.NET project seems to require
that the person have the entire project checked out to them (unlike the
way it works in Access).  

Has anyone else encountered these things?  If so, are there solutions?
Or...if these are just known VSS hassles, do you have any suggestions
about other source control solutions that work well with .NET?

Thank you!

Steve Capistrant
scapistrant at symphonyinfo.com
Symphony Information Services
7308 Aspen Lane North, Suite 132
Brooklyn Park, MN  55428
763-391-7400
www.symphonyinfo.com





More information about the AccessD mailing list