I don't know how many users you have when you say "many".
About a year ago, I started development of a major app
that would host 40-50 users, using an Access mdb, with
ADO.NET. Before I passed 5 users, I was get corruption
more than once per day. I switched to SQL Server to get
around the problem. Access is a great desktop database,
but I seriously doubt that you are going to be able to
sustain "many" users doing updates without incurring
corruption and "Admin machine locks...."
Others may not agree with me, but I've been working with
it for years and never had much luck with more than 4-5
users doing updates simultaneously.
You can try building your own record locking system into a
table in the database. This tends to funnel users (slow
down the number of simultaneous users attempting to
update). That is an option that cuts down on the "Admin
Machine" locks and obviously will reduce corruption.
Access is single thread and throwing too many updates at
the same time tends to cause problems.
Wish I had a better suggestion, but the Access engine was
never designed to be industrial strength client server
database, in my humble opinion. Again, it is very user
friendly and easy to use from a programmer and maintenance
standpoint, but the uptime under heavy use is a problem.
Les Smith
See Add-ins, books, NetCommander at HHISOFTWARE.com
KNOWDOTNET.COM coming soon.
-----Original Message-----
Hi,
I wrote a program in C++. That program writes Data
to ACCESS 2000 Database with DAO 6.0 from many
Client-Workstations to one Server-Workstation, which
had the called database. Writing to the database
generates multiple times in a day a broken database.
Which must be repaired.
What can I do to find out what is the reason for this
problem ?
Best regards
Axel Lanser
.
