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. Check in Log to make sure no one else has un-rolled changes; if they are, coordinate with them
2. Make sure the change is documented in Log, individual changes can be marked minor; mark as not rolled out yet at top of heading
3. Make sure the version in the version table in the program has been updated to the date of the first set of changes since the previous version; this field drives the version number collectors see on their main screen
4. 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-01-03; 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
5. Roll out the changes
   1. run the file updt_all.bat
   2. when the file is done, it will show a log; review if you want to or just close, it's really just for keeping track.
6. update in Log that an update was rolled out; this edit should have minor edit un-checked.

Rolling out a change to CCMDB_data.mdb

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.

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, which checks if the current version of the CCMDB_data.mdb is as stated 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.

1. make sure any changes are documented on the wiki, ie new articles for new fields.
2. open CCMDB_data.mdb_Change_Log and document change
3. add the fields/make the changes
4. update version in table A_Info
5. close and don't copy to server yet
6. open CCDMB.mdb and Log
7. change version in version table if not already done
8. update the version number for ccmdb_data in Module DB_Converter, Sub Convert_DB
9. check to make sure your specific change doesn't require other changes to DB_Converter
10. Roll both CCMDB.mdb and CCMDB_data.mdb concurrently

Rolling out a change to Centralized_data_front_end.mdb

Set up the entire environment on your computer that is needed to run this.

1. check Centralized data front end.mdb Change Log 2016 to make sure no one else has un-rolled changes; if they are, coordinate with them
2. start logging change in Centralized data front end.mdb Change Log 2016
3. make the changes on your PC
4. roll the update to the master location
5. document in Centralized data front end.mdb Change Log 2016 that you rolled out

The next Pull will download the change to others.