One thing to note is that if someone abruptly disconnects from a database, a"corruption flag" may be set.
This will mean that the database is in a corrupt state.
Anyone attempting to access the database will receive a message and the database will have to be repaired.
If it is not repaired in good time, it will bring about loss in productivity as well as frustration from users.
Here are some pointers that will minimize the probability of data loss for your database.
Database Splitting: Here one can split the "front-end" parts from the "back-end" parts.
The front end parts may include forms, reports and queries while the back-end parts contain only the data tables.
A copy of the front end is placed in each user's computer while the back-end is placed in a shared folder within a network.
This means that the data tables don't have to be moving from user to user because it is in this movement that data tables become corrupt hence loss of data.
If one may be experiencing corruption problems with a database on a network, splitting it is important to stop this.
Avoid holding open connections to database: After getting access to a database, it is always important to close the connection after one is through with what they are doing.
Leaving open connections will allow more opportunities for 'unwanted' dropped connections i.
e.
automatic closing of the connection.
Always exit the database correctly: It is advisable to always exit the database correctly.
Some shortcuts such as pressing Ctrl-Alt-Del can bring about major problems on ones database.
It is a good practice to exit the database the correct way.