Rolling out changes

Changes to the master version of CCMDB.mdb needs to be tracked in the Change Log and rolled out to all locations.

Rolling out a change to the CCMDB.mdb

This includes changes to the s-tables, the graphical interface and the programming/logic.

1. Make sure the change is documented in Log
2. Make sure the version in the version table in the program has been updated to the data of the first set of changes since the previous version
3. Copy the new version to the Master directory
   1. Open Regional Server\Programs\Master
   2. Rename the file CCMDB.mdb to version it, e.g. to CCMDB.mdb.pre_2010-jan-3; this will also prevent opening it accidentally since it removes the file association with Microsoft Access
   3. Move the renamed file to the Versions folder
   4. Copy the new version of CCMDB.mdb to the Master directory
4. Roll out the changes
   1. run the file updt_all.bat
   2. when the file is done, it will show a log; scroll to the end of the log and make sure that all locations received the newest version; if a location didn't, contact them to get them to log out of the program and copy the file manually or re-run the batch file

Rolling out a change to CCMDB_data.mdb

This includes changes to the data structure that collected data is stored in, i.e. the l-tables.

When CCMDB.mdb starts the form Main Form is opened. It's open event triggers a call to VBA function Database_Starter() in module Global_, which in turn calls function DB_Converter module DB_Converter.

This string of code checks if the current version of the data is as hard coded in that code; if not it copies down a new version and transfers the data.

Of course this needs to be changed to accommodate the change in the data necessitated the change in the first place.

This process only works if the laptop is attached to the network the first time CCMDB.mdb is started after the new version is downloaded. Data collectors need to be alerted of this. Or, the process needs to be changed to not require this...