CCMDB.accdb: Difference between revisions

WGobert (talk | contribs)
TOstryzniuk (talk | contribs)
mNo edit summary
Line 2: Line 2:


Each PDA has a combo of two ACCESS databases associated to it: a '''ccmdb.mdb''' file which is identical for all until synced into, and a [[settings.mdb]] which contains location specific information such as the path to the [[Regional Server]], and the hospital and ward names. Any data in the ccmdb.mdb is considered transient, the file can be replaced with an empty new version at any time. Rolling out new versions is done by batch and a file that is currently open will not be overwritten.
Each PDA has a combo of two ACCESS databases associated to it: a '''ccmdb.mdb''' file which is identical for all until synced into, and a [[settings.mdb]] which contains location specific information such as the path to the [[Regional Server]], and the hospital and ward names. Any data in the ccmdb.mdb is considered transient, the file can be replaced with an empty new version at any time. Rolling out new versions is done by batch and a file that is currently open will not be overwritten.
Additionall'''Bold text'''y, this programs folder contains a \Master directory where the master version of the ccmdb.mdb is stored. Any changes required to the program can be made on this master file, and then rolled out by copying the master\[[updt_all.bat]] batch file to a local drive (batch code can’t cope with running from an unnamed drive) and running it.  
Additionally, this programs folder contains a \Master directory where the master version of the ccmdb.mdb is stored. Any changes required to the program can be made on this master file, and then rolled out by copying the master\[[updt_all.bat]] batch file to a local drive (batch code can’t cope with running from an unnamed drive) and running it.  


== Change Log ==
== Change Log ==