Skip to content

Keeping track of updates to the access application

June 4, 2013

Now that I am making regular updates to the code of this DB.  I need to identify an intelligent way to track and manage the changes.  A quick recap.  This application has two DBs.  One stores the code, the other stores the tables/data.  I think it a good design.  I am updating the code DB, not the data.

I have made several updates / fixes to the code and have been renaming the code DB appending the date to the end of the file name, like this:

estec_code_2_19_13.mdb

estec_code_3_14_13.mdb

estec_code_4_21_12.mdb.

After I make an update, and my customer agrees, I change the properties of the shortcut on their desktops.  They have 2 workstations where they use the application from.  Each has a shortcut on its desktop that points to the code DB that is stored on a network server.

As I discovered this am, only one of the workstations can have the application open at a time.

After I make a new update, I move the old version into a folder called estecDBs. This way, I have all the old DBs on the network still and could go back to a previous *build if necessary.

I also keep a document synched with the updates that says what was changed on each update. I store that document in the same folder as the old dbs.

Advertisements

From → MS Access

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: