What can I do to help prevent data file corruption and/or data loss?

OneSource data is currently stored in an MS Access database file.  Like all databases, MS Access data is stored in digital format and requires a stable electronic environment to store and save data properly.  The following list can help to prevent or troubleshoot data file corruption problems:

1. Keep the power to all PC's and your server constant and steady by connecting your PC and Servers into a UPS (un-interruptible power supply) battery/surge protector.

2. Don't ever turn off your PC or server without first logging out of OneSource first.

3. Avoid using low quality network interface cards (NIC's).  Poor quality or faulty network cards may work fine "most" of the time, but lose connectivity now and then.  When a network card randomly looses connection before new or changed data is written to the database file data corruption and loss of the changes to the record can occur.

4. Avoid using low quality or damaged network cabling, networking hubs/switches, etc.  If a wiring problem is suspected, you may want to ask a networking professional to run a wiring test.

5. When possible, avoid using wireless networking network cards and switches.  Wireless networks can occasionally simply loose connection which can cause data file corruption.

6. Avoid holding connections to the data file open for very long. When entering or changing data, save unsaved data routinely.  In most cases, all records on the screen/form are automatically saved when you close the form, browse to another record, or press Ctrl+S.

7. Do not reboot your file server when others have a connection to the data file on the file server.  

8. Look in all PC or Server Event Logs for any errors signifying loss of network connectivity or an MS Access crash (such as EventID: 1000)

9. Turn on the Event Log in OneSource and review it the next time a problem occurs to determine if any users login into OneSource but do not log out of OneSource--signifying inproper log off (MS Access crash, faulty network cable, etc).  This may help to narrow down the culprit PC.

10. If you are using OneSource is a Terminal Server environment, it is imperative that the server not be shut down or rebooted when any users have any files in the read+write state on the server.

Note: If the problem persists, an excellent alternative network configuration option is to setup OneSource for use in a Windows Server 2000/2003 Terminal Server environment.  Terminal services allow users to log in and use applications directly on a server.  The upsides to this type of solution are (1) easier access to OneSource from a remote location, (2) virtual elimination of the problems listed above (except the last item)--since the data never leaves the server, (3) depending on the speed and amount of your server's processor, RAM, and hard drive, this may provide a significant increase in network performance speed.