Serious error in database

  • Thread starter Thread starter Wildinthemild
  • Start date Start date
W

Wildinthemild

My dear,

I ahve a serious problem. One of my ckients who is
using a Microsoft Access 2000 database is complaining
about the following error which occurs frequently.

I have developed a program in VB with access as back
end. Its a multi user system with a maximum of 10 people
using the software at a time.

The database gets corrupted always and it cannot be
repaired. Always we have to replace with the back up file.

The error it gives is "This mdb file needs to be
repaired or is'nt a database file. You or another user
may have unexpectedly quit MS access while an access
database was open". Do you want to repair database?.

When we select the yes option it shows

"This MS Access database cannot be repaired or is'nt a
database file". Why this happens often. Is MS access not
suitable for multi users accessing the same database
simultaneously. Or is it an error in the programming side.
Plase do reply at the earliest.
 
The error message indicates the database is corrupt. This is not normal, so
the solution will be to identify why it is corrupting frequently. It usually
comes down to interrupted write operations.

First thing to check will be the network. Are they attempting to use Access
across an unstable network such as WiFi? WAN connections? Running Access
locally on data across an unstable network will corrupt it. If it is a local
area network using standard ethernet, how good are the connections?
hubs/switches? NICs? Lots of collisions?

If that is not the issue, have you split the database so each workstation
has its own local copy of the front end? That's essential for stability, and
preferably use MDE files for the front ends, since they will not decompile.

Ensuring that *all* machines have the latest service pack for Access 2000
(SP3), and also for JET 4 (SP8) will make a difference also.

If the problem is not yet resolved, consider adding a routine to log users
in and out as the open/close the database. You can get the name of the
computer from this code:
http://www.mvps.org/access/api/api0009.htm
Now examine the log to see if there is a particular machine that is logging
in, but not out. If so, trace down whether that is due to faulty hardware,
network issues, or a user who can't be bothered closing down properly. That
should lead you to solve the problem.

For more information, see:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html
 
Back
Top