Asked By
bentot
0 points
N/A
Posted on - 08/11/2011
Hello guys,
The question that I am posting here is about a database that keep son having inconsistent state, just like what is happening now, early in the morning when I try to open the database, I get again the same error I get the past days.
Microsoft Office Access
Microsoft Office Access has detected that this database is in an inconsistent state, and will attempt to recover
the database. During this process, a backup copy of the database will be made and all recovered objects will be
placed in a new database. Access will then open the new database. The names of objects that were not
successfully recovered will be logged in the “Recovery Errors” table.
OK
What is good in here is that Microsoft Access can manage in repairing it, but it takes time. I am now asking for some help on how to avoid the situation like this because every time this happens, a lot of time is wasted. Please write some comments on my issue. Thanks a lot guys.
The database is in an inconsistent state
Data source corruption will not have a "common" situation. You will find, nonetheless, a few practically assured approaches to corrupt a good MDB. If you power down your computer or perhaps "crash" your computer, or, in the case of server-based directories (Which includes peer-to-peer systems) collision the particular community host or fall the actual network link, it is almost an assurance.
When the Netware servers are usually away from space, Netware might clear caches just before creating the information, which could damage open entry files. Should you abandon the machine centered entry program available on the workstation as well as the host manager "kicks you off the net" and reboots the particular host, probably the MDB is damaged.
If you work with terminal host and the people remove, instead of record off the machine, corruption might happen once the machine is shut down. This particular is similar to yanking the ability put on your computer while you've kept programs running as a possible arranged shutdown of the software will not happen before the record off method is finished.
The database is in an inconsistent state
Having a database in a server which has forms, queries, reports, modules or macros causes many issues. When multiple users are accessing the database over the network, the objects corrupts easily especially when the network is slow.
The best thing to do about this is to have the database split. You can use the database splitter on the menu under the database utilities.
Do this splitting in the local copy only. After splitting the database, move the files with only the tables (back end) to the server and give each client user a copy of the front end. With this, if a user corrupted his copy of the front end, you can just give him a new copy while the data remains safe.
