[AccessD] SourceSafe

Charles,

Without reading the entire web-site you provided, are you using this for MS
Access? I didn't see MS Access in my quick look. If you are using it for
Access, what do like about it that is better/improved over VSS. I'm coming
from the angle that I think VSS is pretty buggy after using it almost 2
years. Any downside using what you suggest over VSS?

Thanks,

Scott

-----Original Message-----
From: Wortz, Charles [mailto:CWortz at tea.state.tx.us]
Sent: Friday, August 01, 2003 9:25 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] SourceSafe


Jim,

Unless you have finalized your decision to go with VSS, may I suggest
Merant's PVCS Version Manager, see www.merant.com.  We used VSS for
several years and decided to switch to VM a year ago and we haven't
regretted it.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us



-----Original Message-----
From: Jim DeMarco [mailto:Jdemarco at hshhp.org] 
Sent: Friday 2003 Aug 01 08:01
To: AccessD (E-mail)
Subject: [AccessD] SourceSafe

We are in the process of purchasing Visual SourceSafe as we've really
not been managing our code up to this point.  My question is, is there a
difference between the stand-alone version and the version that ships
with Visual Studio (we have VS 6 licenses)?  I'm under the impression
that the VS version can't be run on our network but stand-alone is
designed for this.  Is this true?  I can't get a sense of this from the
M$ site.

TIA,

Jim DeMarco
Director of Product Development
HealthSource/Hudson Health Plan


_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com