Access database life

[Pietro]

Hi,
Three days ago,I've designed an access-based application that's used by
around 40 users,around 1000 rows are entered per day by users,I'm just
worried abut the life of this database,is it true that Access has a maximum
number of recorods and that after this number the database will be corrupted
?,I've deset all forms to lock the records that are edited by another user to
avoid any conflict,what else should i do to protect my dataqbase from being
corrupted...please advise I'm very worried.
Thanx

 

[Daniel Pineault]

Take a look at http://www.databasedev.co.uk/access_specifications.html

You can also google the subject to get lots more info on access'
limitations/specifications.

As for avoiding corruption...
ensure your db is split and that each user has their own front-end.
do back-ups on a regular basis
perform routine maintenance including compact and repairs.

Also, Tony has an entire section devoted to db corruption. Here is a link to
the causes section... Fell free to check out the rest of the site.

http://www.granite.ab.ca/access/corruption/causes.htm

 

[John W. Vinson]

Hi,
Three days ago,I've designed an access-based application that's used by
around 40 users,around 1000 rows are entered per day by users,I'm just
worried abut the life of this database,is it true that Access has a maximum
number of recorods and that after this number the database will be corrupted
?,I've deset all forms to lock the records that are edited by another user to
avoid any conflict,what else should i do to protect my dataqbase from being
corrupted...please advise I'm very worried.
Thanx

There is no specific maximum number of records - a .mdb file is limited to 2
GBytes. Million-row tables are no big deal if your application is designed
correctly; I know of some working databases with 20,000,000 rows in the
largest table. If you need more than that, consider storing the data in
SQL/Server and using Access as a frontend.

You've been given a link to Tony's excellent corruption FAQ, but... asking how
to keep your database from being corrupted is a bit like asking how you can
keep your car from being damaged in an accident. With the car, you drive
carefully and try to avoid accidents, and carry insurance; with the database,
you drive carefully and try to avoid accidents, and maintain regular backups.
As a rule of thumb for backup frequency, always make a backup before the point
where reentering the data since the last backup would become a real problem
rather than just an irksome chore. This might be monthly, daily, or every half
hour depending on your application.

For a multiuser system it's ESSENTIAL!!! that you use a split application : a
shared backend containing the tables, and each user using their own copy of a
frontend containing everything else.

John W. Vinson [MVP]