Version Manager

Topic

New Reply

Here’s a little idea I came up with recently that may be of use to some: A table to record version/development information for projects under development (or just fine tuning).

I set up a table with three fields: Version (autonumber), Date, and Notes (memo field). Then a form was set up to easily enter new information or review notes about previous changes.

Currently I am working together with another programmer, and this setup allows us to keep up on the changes that each of us are making.

Reply | Quote

Replies

I have done the exact same thing except I have a module that is called on the on open event of the startup form. When the form opens it compares the version of the copy on my desktop to the version listed in backend (be that SQL Server or Access on a network drive). It sends up a message box with the notification, and the comments section. This allows my users to know that there is a newer version available. I have a DOS batch file that copies the front-end down from the network drive. I can either let the batch file be executed by the user or call it from the module (it depends on my users/requirements whether I automatically kick down the upgrade or not).

Reply | Quote

In retrospect I don’t think I made that clear. I have two tables that get the exact same data copied on to them. One table resides on the front-end (of a split database) the other resides on the back-end. The module compares the two tables, if the back-end has a newer version, then it copies the latest copy of the front-end down from the server.

sorry ’bout that.

Reply | Quote