CCMDB.accdb: Difference between revisions
TOstryzniuk (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. | ||
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. | 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 == | ||
Revision as of 23:10, 2008 December 29
The CCMDB.mdb is the ACCESS program the PDAs sync into. It screens the data for internal consistency and ranges, and then exports it in a format that can be imported into TMSX or MedTMS.
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. 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
Starting 27 May 2008 the change log will be stored in the.
See Change_Log_2009for the latest.
TOstryzniuk 23:08, 29 December 2008 (CST)
Additional Info Required
some of these as separate pages
- Checking your Data in Access
- starting Access
- filtering to complete only
- Yellow fields and error messages
- Sending your data
- Deleting data once you have the OK, ...
Discussion
- data collectors must participate and fill this information in.TOstryzniuk 22:31, 29 October 2008 (CDT)