CCMDB.accdb requires password when closing: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
 
Line 8: Line 8:
The only solution seems to be to revert to an earlier version and re-apply the changes that were done. If the changes were extensive it might be quicker to import the module/form/etc that was changed from the corrupted version, but that too can be tricky. This happens to Tina during programming about once a month, but isn't usually encountered by others since they don't work with the code or data structures.  
The only solution seems to be to revert to an earlier version and re-apply the changes that were done. If the changes were extensive it might be quicker to import the module/form/etc that was changed from the corrupted version, but that too can be tricky. This happens to Tina during programming about once a month, but isn't usually encountered by others since they don't work with the code or data structures.  
   
   
* Steps to Identify the Clean Verion and revert to an earlier clean version
* Steps to Identify the latest clean version to revert to:
** In the regional server \\ad.wrha.mb.ca\WRHA\REGION\Shared\ICU_DATA_COLLECTION\Programs\Master\Versions, check the previous versions for one that may be larger than the others, it is usually around 12-13,000 KB, choose the most recent clean version based on this
** In the regional server \\ad.wrha.mb.ca\WRHA\REGION\Shared\ICU_DATA_COLLECTION\Programs\Master\Versions, check the previous versions for one that may be larger than the others, it is usually around 12-13,000 KB, choose the most recent "normal" sized version based on this
** once identified copy the clean version and put it on the desktop, make sure you don't have the database open
** close database if you currently have it open
** rename to CCMDB.accdb
** copy the clean version and put it on the desktop
** open this copy and reapply any changes (look at the CCMDB change log)
** rename to CCMDB.accdb, removing the postfix we apply to old versions
** copy this new version from the desktop and put it in the C:\ccmdb_program
** open this copy and reapply any changes (look at the [[Log]])
** copy this new version from the desktop and put it in the C:\ccmdb_program, overwriting the broken version that is currently there
** follow the usual steps for [[Rolling out changes]]
** follow the usual steps for [[Rolling out changes]]


== Related articles ==  
== Related articles ==  
{{Related Articles}}
{{Related Articles}}

Latest revision as of 10:58, 2024 August 28


Occasionally after changing something in the programming of CCMDB.accdb it starts requiring a password on closing.

If this happens on a data collector laptop

Try Copying down a clean version of CCMDB.accdb.

If this happens during updating of the program by main office

The only solution seems to be to revert to an earlier version and re-apply the changes that were done. If the changes were extensive it might be quicker to import the module/form/etc that was changed from the corrupted version, but that too can be tricky. This happens to Tina during programming about once a month, but isn't usually encountered by others since they don't work with the code or data structures.

  • Steps to Identify the latest clean version to revert to:
    • In the regional server \\ad.wrha.mb.ca\WRHA\REGION\Shared\ICU_DATA_COLLECTION\Programs\Master\Versions, check the previous versions for one that may be larger than the others, it is usually around 12-13,000 KB, choose the most recent "normal" sized version based on this
    • close database if you currently have it open
    • copy the clean version and put it on the desktop
    • rename to CCMDB.accdb, removing the postfix we apply to old versions
    • open this copy and reapply any changes (look at the Log)
    • copy this new version from the desktop and put it in the C:\ccmdb_program, overwriting the broken version that is currently there
    • follow the usual steps for Rolling out changes

Related articles

Related articles: