Version Control for Application

[Jim Dudley]

Access 2010
Windows 7
User Skill: Db - Intermediate
Macros - Novice
VB - Pre-Novice

My application will be divided into BE & FE Files when finished.

I am looking for input(articles) on Best Practices for Version Control. To be used to keep track of what changes have or have not been made at installation sites of the application. I would envision 2 sets of numbers. One for the FE File and One for the BE File. Possible a small Db to record the changes with Linked Word Docs in a Field that contain descriptions of each versions' changes.
Any suggestions for reading material or posts? I did a Search on 'Version Control' but found nothing.

Thank you.

Jim

 

[RuralGuy]

Here's a link you might find useful: http://allenbrowne.com/ser-09.html

 

[gemma-the-husky]

i think most people do what you suggest

have a common back-end field stipulating the required version number

have a local front-end field stipulating the version number of the current front end. If the local version is not correct, then quit the app.

There are then a number of auto-update tools to collect the new updatred database.

I tend to just have a table in the front end recording details of applied mods, but you could equally keep a version hitory text file in the same folder as the back end.

 

[Lightwave]

I tend not to version the backend and have a simple label on the front end and whenever I make changes I increment the front end version label. 2.1 /2.2/2.3 etc.. works for me so far. Although I could see having a table in the front end might have some advantages.