Record limit

[DiamondDug]

This question is related to another post of mine about "Invalid Arguement"
error (I think). Is there a size limit to the number of records you can have
in a single Access Database? I posted yesterday about receiving an "Invalid
Arguement" error after creating a number of Make-Table Queries. After I had
gotten the error I was unable to manipulate anything in my database. I
couldn't create a new table. I couldn't delete records from existing tables.
I couldn't run any Make-Table Queries. I assume that there is a limit and
once this limit is reached the user is presented with this problem.

Is there any truth to my assumptions? Thank you.

 

[Rick Brandt]

This question is related to another post of mine about "Invalid
Arguement" error (I think). Is there a size limit to the number of
records you can have in a single Access Database? I posted yesterday
about receiving an "Invalid Arguement" error after creating a number
of Make-Table Queries. After I had gotten the error I was unable to
manipulate anything in my database. I couldn't create a new table. I
couldn't delete records from existing tables. I couldn't run any
Make-Table Queries. I assume that there is a limit and once this
limit is reached the user is presented with this problem.

Is there any truth to my assumptions? Thank you.

No record limit, only a size limit on any single file. 1 GB for A97, 2GB for
newer versions. I have never had a file approach the limit, but "acting
weird" is what I have seen posted as to what happens when the file gets to
the limit. I don't know if there is a consistent behavior or error that
occurs.

 

[Nikos Yannacopoulos]

To the best of my knowledge, no such limit exists. There does exist a
total database file size limit, though, and that is 2GB. If you have
been experimenting with make-table queries, then there is a very good
chance they have introduced some serious bloat. Is your file size near
the 2GB limit? Do a Compact and Repair and see what happens. That
failing, create a new, empty database and import all objects from the
previous one to obtain a new, clean copy.
At any rate, frequent compaction of *any* database is good for its
health, so make sure you do that. For a single user, monolithic
database, the Compact On Close (Tols > Options, General tab) available
in A2k and later, is a good solution.

HTH,
Nikos

 

[kabaka]

I bump into the 1GB limit (I'm on A97) every week which requires a Compacting
and I've never had any of the troubles you describe.