Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
TOstryzniuk (talk | contribs) m Ccmdb corruption moved to Ccmdb program corruption |
TOstryzniuk (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
when opening Access [[CCMDB.mdb]], cannot view dropdown list in labs, or pharm or even the DX codes. Weird things in note section......to name a few things. Access has seized up on local laptop for reason unclear..... | when opening Access [[CCMDB.mdb]], cannot view dropdown list in labs, or pharm or even the DX codes. Weird things in note section......to name a few things. Access has seized up on local laptop for reason unclear..... | ||
*Manually replace the CCMDB.mdb in the Program folder on local laptop C drive. | *Manually replace the [[CCMDB.mdb]] in the Program folder on local laptop C drive. | ||
#Close ccmdb on laptop. | #Close ccmdb on laptop. | ||
#*From the [[Regional Server]], '''manually copy''' ccmdb.mdb from: Programs/Master folder | #*From the [[Regional Server]], '''manually copy''' ccmdb.mdb from: Programs/Master folder | ||
Revision as of 16:11, 13 October 2010
when opening Access CCMDB.mdb, cannot view dropdown list in labs, or pharm or even the DX codes. Weird things in note section......to name a few things. Access has seized up on local laptop for reason unclear.....
- Manually replace the CCMDB.mdb in the Program folder on local laptop C drive.
- Close ccmdb on laptop.
- From the Regional Server, manually copy ccmdb.mdb from: Programs/Master folder
- paste to local laptop C: drive into the ccmdb_program folder.
- run news and backup
- close out of ccmdb.mdb
- on local laptop C: drive, go to ccmdb_data folder.
- open ccmdb.mdb with usual password. IMPORTANT NOTE: will only see L_files.
- at the top of the screen tab, click on TOOLS
- select Database Utilities
- select Compact and Repair Database
- close out of Access by clicking the "X" in the top right corner.
- on local laptop C:drive, go to ccmdb_program folder.
- log back into ccmdb.mdb with usual password. Problem should be resolved.
--TOstryzniuk 17:08, 13 October 2010 (CDT)