Rolling out changes
Changes to the master version of CCMDB.mdb and/or the S_ Tables need to be tracked in the Change Log and rolled out to all locations.
Rolling out a change to the S_Tables
A change to any of the S_Tables needs to be done both in CCMDB.mdb and in HanDBase; ensure that the changes are identical since differences can cause problems in error checking. See [[#Rolling out a change to the CCMDB.mdb| the next section]] for how to roll out changes to the CCMDB.mdb.
To make a change to an s_ table in HanDBase:
- Open the Master folder for Handibase S_Tables in REgional Server\S_Handibase
- make a copy of the file you will change and rename it to version it, e.g. to S_Tmp.pdb.2010-feb-11; this will also prevent opening it accidentally since it removes the file association with HanDBase
- open the table; you must have HanDBase installed on your computer to do this.
- make the change
The updated table should be automatically uploaded to every PDA upon the next sync. If the changes are not uploaded automatically, the local data collector can get the update by following the instructions in Manual pull-down of s tables to PDA.
Rolling out a change to the CCMDB.mdb
- Make sure the change is documented in Log
- Copy the new version to the Master directory
- Open Regional Server\Programs\Master
- 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
- Move the renamed file to the Versions folder
- Copy the new version of CCMDB.mdb to the Master directory
- Roll out the changes
- run the file 'updt_all.bat
- 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