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.

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

To roll out changes to the l-tables is a lot more messy. I will need to write it up when I have figured out a clean process. Ttenbergen 16:56, 1 November 2010 (CDT)

Rolling out a change to the CCMDB.mdb

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.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