[AccessD] Access + SubVersion

We don't use SubVersion, but we moved from VSS to SourceGear.  We looked at the Team stuff and decided it required too darn much effort to implement for a small team.  Plus it required SharePoint services which is a headache in itself.  Out project manager explored it and decided we simply didn't have time for that kind of complexity.  SourceGear is a no-brainer migration from VSS and has some nice features VSS doesn't.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Monday, March 08, 2010 9:51 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Access + SubVersion

Does anyone here use SubVersion as your VCS from Access? I used to use VSS
and was satisfied with it, but it seems this product has gone away in favour
of the Team stuff. I can't afford that upgrade, and so am wondering about
free alternatives such as SubVersion. Does anyone here use this in practise?
How ought one store a Version into SubVersion and then name it and be able
to Restore any Version long after it was captured and stored?

Any bugaboos in using this method are graciously invited.

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