Rolling out changes: Difference between revisions

mNo edit summary
Line 1: Line 1:
Changes to the master version of [[CCMDB.mdb]] and/or the [[s_files | S_ Tables]] need to be tracked in the [[Log|Change Log]] and rolled out to all locations.  
Changes to the master version of [[CCMDB.mdb]] needs to be tracked in the [[Log|Change Log]] and rolled out to all locations.  


== Rolling out a change to the S_Tables ==
This includes changes to the [[s-tables]], the graphical interface and the programming/logic.  
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:
To roll out changes to the L_Files is a lot more messy. I will need to write it up when I have figured out a clean process. [[User:Ttenbergen|Ttenbergen]] 16:56, 1 November 2010 (CDT)
* Open the Master folder for Handibase S_Tables in [[Regional Server]]\S_Handibase
[[Category: Questions IT]]
* 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]] ==
== Rolling out a change to the [[CCMDB.mdb]] ==
Line 23: Line 17:
## 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
## 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


 
[[Category: IT Instructions]]
 
[[Category:IT Instructions]]
[[Category: Change Logs CCMDB]]
[[Category: Change Logs CCMDB]]