By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,105 Members | 1,040 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,105 IT Pros & Developers. It's quick & easy.

Record Limit in Access 97

P: n/a
Does anyone know the record limit for a single table in Access 97? I
have a client who has over 800,000 records in one table. They are
experiencing math problems and timeouts when running reports.
Microsoft's KB didn't seem to have a good answer.

I'm going to try to get them to convert to an Access or custom VB front
end and SQL on the backend, but for now, I need a justification as to
the Access 97 problem.

Thanks!

Bill

Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
bd*****@gmail.com wrote:
Does anyone know the record limit for a single table in Access 97? I
have a client who has over 800,000 records in one table. They are
experiencing math problems and timeouts when running reports.
Microsoft's KB didn't seem to have a good answer.

I'm going to try to get them to convert to an Access or custom VB
front end and SQL on the backend, but for now, I need a justification
as to the Access 97 problem.

Thanks!

Bill


There is no record limit. There is only a limit to how big a single *file*
can get which in Access 97 is 1 gig.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 13 '05 #2

P: n/a
Thanks for the response. I thought there was a limit, but I suppose
not. Is Access 97 known for causing errors once there gets to be a
large amount of data processed?

The database in questions has a "front end" that connects to a "back
end" database. The front end is the interface and it links to the back
end. Maybe if multiple users are working on it, the values could change?

Nov 13 '05 #3

P: n/a
"Bill" wrote
Thanks for the response. I thought there
was a limit, but I suppose not. Is Access 97
known for causing errors once there gets
to be a large amount of data processed?


"Causing errors?" Please clarify.

Particularly if the database uses inefficient approaches to handling data,
vast amounts of data can cause poor performance. On the other hand, a good
many people here have mentioned that they were able to get around the 1GB or
2GB size limit by linking to tables in multiple back-end MDBs. My assumption
was that they must not have been TOO unhappy with performance, or they
wouldn't still be using a database of that size. (I hasten to add that I
have never worked on an Access-Jet database that came close to the limit;
all the large databases I've used were Access clients to various server
databases.)

There _is_ a limit, it's just not a "number of records" limit. I suspect
that the 2GB limit is convenient because of the size of the numeric values
used for internal "pointers" and "indexes", though no one at Microsoft has
made such a statement to me.

Larry Linson
Microsoft Access MVP

Nov 13 '05 #4

P: n/a
Thanks for the quick response. I believe its from old data being linked
in or some other coding issue. Going to check it out....

Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.