1) which SVN for Access dev? 2) alternative for use on peer-to-peer network ?

Question

a - As I understand it typical SVN solutions require a server on your network... true?
b - Which SVN solution should we consider for keeping up with Access development revisions, etc?
c - Is there a solution that will work on a peer-to-peer network?
d - Free alternatives and low coast alternatives are?
thanks for any help.

Answer 1

> As I understand it typical SVN solutions require a server on your network
Sure, “typical” means “many”, so yes. However many others are file based and ONLY require a share folder and thus don't require a server. And then from that shared folder you can often use add-ons to sync that folder to web based systems like GitHub. So
you can "mix" such file only systems and then over time use web based server with that system that does not require a server, but only a shared folder.
>Which SVN solution should we consider for keeping up with Access development revisions, etc.?
Actually, you can just simply “copy” the current version to some folder before you “release” that version. So copy and add a “version” number to the accDB file. If you application is MyInvoice.accDB, then copy to server with MyInvoice-1044.accDB (verison
1044). Since Access is a “single” file, then this works rather well compared to other systems that have “many” files. In fact I copy both the accDB, and the compiled version accDE to a folder on the server (with version number added to the file name as per
above). Thus you can go back to any previous version with great ease.
However, you might be talking about source code control in addition to versioning of software. (often the term is interchanged, but it should not be). Source code control (SCC) is a “common” means to achieve versioning of software, but ALSO allows multiple
developers to work on the project at the same time (collaboration). So there is a big difference between SVN, and SCC.
Access for a VERY long time has supported Microsoft “standard” source code control interface. While Access is a “single” file, Access is able to “logically” view each application part as a separate file. So the fact of “one” file, or “many” files does not
matter – say no more then a zip file is “one” file, but inside there are “many” files! So SCC is 100% possible in Access, and since Access has a resolution down to an object by object basis? Then developers can check-in/out individual forms, query
code modules etc.
Access versions all the way up to 2010 support the “standard” Source Code interface.
So:
Using GitHub you see this:
Using VSS, you see this:
Note that using Git, TFS, VSS etc, they ALL give the above UI with check boxes beside each object, and all give a cool "check in/check out" right click context menu not shown above.
The above Git shot is running in "file mode" without a server. Visual Source Safe is also file based, but VERY old and quote hard to find now.
So the great news is that Access has for a very long tie supported SCC, and thus is a great way to “version” your software. And Access will show you OBJECTS that are checked in/out by you as per above with the check mark and lock icon.
So inside of the access GUI you could with any SCC system that supports the standard SCC interface would know what objects are locked and you not taken ownership of. (note the "lock" and "check mark" icon beside each object.
However, Access 2013 dropped support for SCC. So all of the above cool options are NOT available for 2013.
Since Access is a “single” container, then versioning tends to be rather easy. Just copy the file to a folder with a version number appended to the file name, and you are done!
You not distinguished between versioning of your software, and that of source code control – so it not clear if you looking to just keep versions of your software, or allow team development on your application?
While SCC will give you versioning, it also allow multiple developers to work on the same application at the same time (collaboration). SVN does not necessary give you this multiple developer ability.
As noted, versioning for Access is easy - just copy the accDB (front end) to a folder on the server with a version number appended to the file name. Works quite well. I have a table in the front end with a version number, and a version number in the back
end table. My deployment code reads that version number and copies the files to the server for me.
(It is assumed that you have a split database).
However, if for 2013 you need both versioning and SCC (say to allow multiple developers), then you likely have to roll your own. I would suggest using “save-as text” command to export all access objects to a folder, and THEN use one of MANY source code control
systems that operate on that folder. Such a setup could easily be cobbled together in an afternoon of your time. And “many” SCC systems provide a GUI that is external to the developer tools/environment. This would allow you to use free tools like Git and GitHub.
For just versioning of your software? Then SCC is likely overkill, and if you using Access 2013, then you cannot use standard SCC providers anymore anyway.
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada