Version Control(s)

[Tom Cone Jr]

As I've started developing applications for others I've discovered that it's difficult to keep track of who has what. This is especially difficult for folks who have the same app, but different 'versions'.

I'd appreciate any tips, pointers or suggestions on how folks organize their development systems to keep up with this kind of thing.

At the moment, for example, when I add a new feature to the core application, I find myself repeating it in all the other customized versions that are 'out there'. This is error prone and tedious, to say the least. A few more customers and I'll go out of business!

-- tom

[JerryBrightbill]

RE: Version Control(s)

Tom,
I have the same problem, particularly when I am letting a user test a prototype app. Hard to keep track of what they have. I have started to use build numbers to identify each modification level.

First, I created an option on each menu under help that adds an option "About Program". This runs a script that pops up a message box with information about my application. I use a dummy table for menus, dialog message boxes, etc. I save a serial number, registration number and other info in this table. In an autoexec script, I set up a series of global variables, one of which is the current build number. When the MainMenu runs, it populates the other relevant variables. The user clicks the option and gets his program serial number and the current build installed.

The second part of the process is saving changes for each build. I keep a list of changes as I make them (usually) and then when I want to create a new build, I change the build number in autoexec and save all tables, data dictionaries, etc that have changed since the last build in an self extracting zip file. I then change the update zip file to readonly and save it in a separate directory. Then I send a copy to the user/s as needed and have them install it. You could put the build number as a field value in the dummy table, but I like to place it where no one can change it easily.

Since it is easy to forget all of the changes, I finally created a couple of tables and forms to track changes. I attach the tables to an app I am developing. Using one entry form, I start a log record when I start working on the app. When I am done in a particular session, the form will automatically save the start and end times and force me to enter an explanation of what was done. Later, I can create a report that calculates time spent and modifications at each build level.

Hope this give you some ideas. Even using this process, I sometimes forget when I am at (in the developent process, not just physically)

Jerry

[Tom Cone Jr]

RE: Version Control(s)

Thanks. Much food for thought!

--- tom

[Tom Cone Jr]

RE: Version Control(s)

Jerry,
I appreciate your comments. Have been using a simple 'revision date' displayed on my opening menu to distinguish different builds. I think something more specific and complete is needed now, and your ideas have helped.
Spent most of this afternoon sorting my working papers into various notebooks, and backing everything (including the online help) up. Have just about got it organized! It's amazing how fast things get disorganized when you just open an application and start making changes...

-- tom