[AccessD] Access + SubVersion

Hi Arthur

We use an interface to subversion called Tortoise - We don't mind using it
here. it works well enough (Our real developer nerds prefer the command line
version only
     Anyway. once you decide to set up a checkout on Folder X, each time you
make changes to ANY file or files (even adding or deleting) to items in that
folder then those new pieces of information 'go up' with any 'commit'. You
are given the option to type stuff about the commit you are about to make
also.
     If you decide that you need to go back to a certain version then the
'log' feature allows you to review the entire upload/download history for
that checkout location. This is where whatever you type about the 'commits'
is useful.
     There are also file comparison tools built in with this.
     As for filename vs objects - It's file name based. Assume I have
filename called MyCooldB.mdb - I add it to subversion, each change gets
committed and the whole file is placed under version control.

Hope this makes sense

Darren
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Tuesday, 9 March 2010 4: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