Many small business use Microsoft Access to store their data, because it is an easy and economical way. But everyone, who has ever used the database in a shared network, is familiar with the possibilities of corruption that can seriously damage all the hard work invested in it. Of course, you MS Access training will help you solve some of the problems, but you should also know how to reduce the chances of database corruption.
A good thing to do for a networked MS Access database is to split the database into front-end and back-end. The front-end part will contain information that other users will not be able to change. And the back-end will keep the actual data. You can split the database with the help of wizard you have probably learned about during your MS Access training.
The back-end database should be stored on a safe and shared server. You should also make regular backups to this part of the database and strongly protect it from any damages. Archive the front-end database, so because it doesn’t change, even if it gets corrupted due to some reason, it can easily be replaced from the saved copy. The database users can have a shared front-end copy on the server or have an individual one on their computers. The front-end should be write protected for reducing the chances of corruption.
When we use MS Access queries, we often don’t realize how much data it has to read and write. It often surprises the database beginners, how many transactions it takes to perform a query. With this a lot of damages may occur, because every read and write query operation provides another chance for database corruption in case the connection is lost or the system crashes.
But if you store intermediate results to the temporary tables, there are two benefits to it. First, it really speeds up the query. And, second, it prevents the main database from corruption, while moving the risk of any damage to the temporary table. If the temporary table is corrupted, you only lose the query results, but you can easily run another one.
Then you can also split the temporary files. After you learn the techniques of using MS Access temporary tables, you should protect your main database by placing the temporary tables into the separate file. This part of the database should be kept on the back end server. If you separate these pieces of database, it minimizes the chances for the damage spreading to the main database tables. Even if the temporary tables get corrupted, it might have a short term impact on your users and their work, but this piece of database is very easy to rebuild without affecting the rest of the database.
All you need about microsoft access database: great training materials, all sorts of business products (customized for your needs), special microsoft access database blog with tips and tricks about MA databases.
All this and more from a reputable UK based company which specializes in microsoft access database and is helping clients all over the world.