Access is not a true multi-user database system; it has its limitations. It
is just a fact of life that Access is prone to corruption under defined
circumstances. It is most vulnerable if it, the computer/OS it is running
on, or any client that is connected to it, crashes while data is being
written. It doesn't matter who's connected at the time, or how many other
users are connected. If the connection gets dumped during a write operation,
there is a better than even chance that the data store (backend) will get
corrupted.
If you have that many users banging away on this thing 24/7, and if the data
constitutes a financial risk/asset to the company, I strongly recommend you
upgrade the backend to SQL Server, or at the very least, MSDE. If the
frontend has been designed properly (who knows at this stage), you shouldn't
require much in the way of modification.
Just deleting a few records may (or may not) give you a little time before
the thing goes down for good, but take these problems as a warning.
Regards,
Graham R Seach
Microsoft Access MVP
Sydney, Australia
Microsoft Access 2003 VBA Programmer's Reference
http://www.wiley.com/WileyCDA/WileyTitle/productCd-0764559036.html
K2 said:
I'm running a program that writes to the database and is used extremely
heavy each hour. The database is being updated 24 hours a day and is
starting to get very large. About once a week the program will pop up an
error message that says that the path to the .mdb file cannot be found on
the server. The file is physically there though, i've checked. I've heard
from people running similar programs that the database is not supposed to
handle the amount of traffic that is being put through it. Therefore it's
crashing the program. They've said that by deleting a large number of the
records will help solve the crashing problem.
Has anyone else heard of anything like this or know anything like it?
Anything would be greatly apprecitated.
