A
Access Rookie
I am updating a a 5000 record db. I am adding or deleting 200 records a day.
It gives me db needs to be repaired several times a day.
It gives me db needs to be repaired several times a day.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Albert D. Kallal
[email protected]...
You should not need to repair several times a day. I have clients with
applications running all day, (4-6 users), and 60+ related tables. Some of
those tables are in excess of 50,000 records. In 3 years of hard use with 5
users hitting the database all day, they have not experienced ONE corruption
(I have a good number of clients with the above track record.....that means
after 3+ years of hard use, and with multiple users, they have NOT
experienced ONE corruption.
So, what this means is something is wrong with your setup. Compacting the
database is a good thing to do, but HAVING to compact to "repair" means that
something is wrong, and you need to fix this.
I would first split your database, and always give each user a mde front
end. You can read up on splitting here:
http://www.granite.ab.ca/access/splitapp.htm
And, here is the list of stuff to check for the cause of corruptions:
http://www.granite.ab.ca/access/corruptmdbs.htm
You don't mention if in fact this application is multi-user..and how many
users you have. Also, the kind of network connection they use can also be a
factor here.
I am updating a a 5000 record db. I am adding or deleting 200 records a
day.
It gives me db needs to be repaired several times a day.
You should not need to repair several times a day. I have clients with
applications running all day, (4-6 users), and 60+ related tables. Some of
those tables are in excess of 50,000 records. In 3 years of hard use with 5
users hitting the database all day, they have not experienced ONE corruption
(I have a good number of clients with the above track record.....that means
after 3+ years of hard use, and with multiple users, they have NOT
experienced ONE corruption.
So, what this means is something is wrong with your setup. Compacting the
database is a good thing to do, but HAVING to compact to "repair" means that
something is wrong, and you need to fix this.
I would first split your database, and always give each user a mde front
end. You can read up on splitting here:
http://www.granite.ab.ca/access/splitapp.htm
And, here is the list of stuff to check for the cause of corruptions:
http://www.granite.ab.ca/access/corruptmdbs.htm
You don't mention if in fact this application is multi-user..and how many
users you have. Also, the kind of network connection they use can also be a
factor here.
A
Access Rookie
Thanks for your response. There are an average of 8 users on the system.
A
Albert D. Kallal
Access Rookie said:Thanks for your response. There are an average of 8 users on the system.
Great..that sounds like a nice number..well within access limits of use.
So, I guess your now have to sit down and start going through those links I
suggested.
First on the list is to split your database........and give each workstation
a copy of the front end..(preferably a mde).