[AccessD] SourceSafe

Scott,

I am the project team for Access development here and I tried using VSS
when we first got it.  After awhile of fighting it I got an exemption
from the dictat that all development must be done in VSS.  Now that we
have VM and things are going much more smoothly with it I am facing the
prospect of having to move all my Access development to VM.  Version
control is overkill for one man projects in my opinion, but it makes
management feel better.  So all the Access development will be going
under VM within the next few months.

So ask again in about a year when I have some experiences to compare.
That is, if I am still doing Access development a year from now.  <grin>

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: Marcus, Scott (GEAE, Contractor) [mailto:scott.marcus at ae.ge.com] 
Sent: Friday 2003 Aug 01 08:53
To: 'Access Developers discussion and problem solving'
Subject: RE: [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
-----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