PC Tips and Tricks to make your life easier

Reduce The Risk Of Your Database Corruption.

January 19, 2010 By: lilybird Category: Software

There are some data types in the Microsoft Access database that are more prone to corruption. It is better to avoid them if you want to reduce the risk of your database corruption. But sometimes you have to use them, so you should learn how to use those data types properly and safely.

One of the data types is memo fields. They can indirectly cause entire database corruption. And even if you can repair your database, the records stored in the memo fields are usually lost. So, if you had important information stored there, it is lost. But, what if you need to store large amounts of text? One of the alternatives to the memo fields is storing text in a Word format as an OLE object. This method reduces the risk of data corruption and is more efficient for storing a large amount of text. This technique could be learned on advanced Access database courses.

But if you still need to use memo fields, don’t store them in the main table. Place them in a separate table and create a one-to-one relationship with the main table. So, even if the memo table gets damaged, the rest of the data is safe. You will add more protection, if you split the memo table and store the separate file on the back end.

Another big source of corruption to the Access database is the graphic files in Access database. You may learn on your Access courses how to add graphics to your applications and they might be very useful, but still dangerous for database. It would be perfect not to use them, but if you have to, learn to protect your database. To prevent corruption of your database due to the graphic files, you should do the same thing as with the memo fields – store them in a separate table, related to the main table. And put that table to a separate file on your back end server.

If you have taken Access database courses that have covered the last Access 2007 edition, then you must have learned about a new option, which is an attachment. It is a way of utilizing another resource, which is less cumbersome and less intensive storage wise than OLE objects. But the bad thing is they are also prone to corruption. And, again, you deal with attachments, by storing them in a separate table in a different database file. If you use different types of data, each of them should have separate table and a file. It is important to remember that corruption can destroy the entire database, which you have created for so long and which contains so much valuable information. So, the more separation you make the fewer chances you leave for the corruption.

Everything about microsoft access database: great training information, all sorts of business products (that can be tailored for the specifics of your business), special microsoft access database blog with hints, tips and tricks about MA databases.

All this and more from a trustworthy UK based company which majors at microsoft access database and is helping clients round the globe.

Leave a Reply