Compact Repair and Backup

Translate

Member Login

Live Support

Support Service

We are aware of the emergency nature of medical environment and we try to respond adequately. Support is available only to registered users.

FAQs

Office One FAQs

Seven FAQs

Medical Databases

Medical Scheduler FAQs

Medical Articles & Blogs

Enter Blog

Detailed Tutorials

Don't miss the detailed tutorials providing step-by-step guides to getting the most out of our software packages. Learn how to use friendly forms to interactively build your user interfaces, and how to add custom codes

Learn more...

Security Features

HIPAA Compliance

Powered by

Certified Site

Last Updated on Sunday, 10 May 2009 19:46

1. Application maintenance (compact, repair and backup)

2. Why compact and repair databases is so important.

3. What if the standard compacting and repairing procedure does not fix my files?

4. How to avoid database corruption

1. Application maintenance (compact, repair and backup).

The developers of Medical Database Seven ARE NOT RESPONSIBLE FOR DATA LOST WHEN NO RECENT BACKUP HAS BEEN MADE.

·

It is essential that you keep a backup of all files and folders especially the DataMD.mdb file , Photos, ImageFiles, BackupFiles and PatientFiles folders. The DataMD.mdb data file is by far the most valuable application component and you should learn how to backup, compact and repair this file properly.This is your responsibility as a medical professional and a prudent computer user.

·	All data file (DataMD.mdb) maintenance features are available from server side ONLY and you must close all active databases! Repair user interface is available from all stations.

·	The easiest way to maintenance your application is to use the initial application screen.

·	Medical Database Seven comes with an backup feature for DataMD.mdb. Backups are saved into the BackupFiles folder, which is within the Medical Database Seven folder on your main-host computer’s hard drive.

·

Data backup files are stored in File name + Date + Time.mdb format (i.e DataMD_073020081855.mdb where DataMD is file name, 07302008 is the backup date and 1855 is the backup time). You can access this function from "Control Panel" clicking the "Backup Data File" button. Available functions depend on the “Seven” installation type and user permissions. For example you must backup data file from server side of application using the administrator account (server side: the machine with a Full Installation of of Seven).

·

In order to use available functions, you must close all active databases on the network and all locally open forms. If the data folder is shared with other users (where you have a network configuration set up with Seven loaded on multiple computers), confirm that Seven is closed on all other computers in your network except on the computer doing the backup on server side.

·

We recommend that you further back up the whole Medical Database Seven folder onto a CD, Zip disk, or some other removable media so that, if something goes wrong, re-install the latest Seven version and replace the DataMD.mdb, file as well as various folders like PatientFiles from the the backed-up folder without losing data. We recommend using a separate disk for every day of the week.

·	Also you can use the Restore procedure in order to restore a backup data file.

Video Tutorial: Learn how to use the Control Panel functions.

2. Why compact and repair databases is so important.

As you add and update data, a database file becomes larger because Access creates temporary, hidden objects and when you delete such an object, the occupied disk space is not automatically reclaimed. As your database file fills up with the remains of these objects, its performance may degrade. Objects may open more slowly, queries may take longer than normal to run, and typical operations generally seem to take longer. Finally, all of this may lead to database corruption.

3. What if the standard compacting and repairing procedure does not fix my files?

If all fail, you should restore your last backup database that you may retrieve from the /BackupFiles folder at server side of application and renaming it to DataMD.mdb.

In case of front-end corruption (CodeMD.mde) you can restore it from any initial directory backup that you have made or you can run the setup file again in order to replace the damaged file. In this case do not overwrite the DataMD.mdb! because you will lose your data.

Remember that you should always backup the DataMD.mdb and store it in different safe places on a daily basis. A small Disaster Recovery Plan is always useful, especially in order to protect medical data.

4. How to avoid database corruption :

1.	Avoid power failures during database writes. Always use a UPS unit.

2.	Do not close network connections.

3.	Avoid power loss, manual shutdown and shutdown the application with task manager.

4.	Compact the database often.

Typical Symptoms of a Corrupt Microsoft Access Database

·	Unrecognized Database Format

·	The Microsoft Jet Engine cannot open this file

·	You do not have the necessary permissions to open this object. Please contact your system administrator.

·	Enter database password - even though none was set up

·	The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time

·	....... Look in the index collection of the TableDef object to determine the valid index names

Quote this article on your site

To create link towards this article on your website,
copy and paste the text below in your page.

Preview :

Compact Repair and Backup
Monday, 03 March 2008
1. Application maintenance (compact, repair and backup) 2. Why compact and repair databases is so important. 3. What if the standard compacting...