Size restriction?

[Dan]

Hi,
I will need to create a database with 10 fields and 500,000.
Iss that something that Access 2003 will be able to handle.

I could find that Acces 2003 can handle up 2 gigabytes, but I do not know
how to calculate if 10 x 500,000 data will pass that limit.
ANy idea.
Many thnaks,
Dan

 

[Allen Browne]

Access is fine with 500,000 records in a table.

The actual space depends on the actual data in the field. Estimate how many
bytes will be in a typical record, e.g. 10 fields averaging 35 bytes = 350
bytes, plus some overhead for the fields and record, so say 400 bytes per
record, times 0.5 million records = 200MB.

That's *very* rough, and assumes there's no deleted (uncompacted) data, no
other objects, no graphics/logos etc. But you get the picture.

 

[John W. Vinson]

Hi,
I will need to create a database with 10 fields and 500,000.
Iss that something that Access 2003 will be able to handle.

I could find that Acces 2003 can handle up 2 gigabytes, but I do not know
how to calculate if 10 x 500,000 data will pass that limit.

The limit is not on the size of a table but on the entire size of the database
- tables, forms, queries, code, system tables, etc.

That said, what you're asking is sort of like "Will my truck carry 500,000?"
500,000 of WHAT? You have ten fields: are they one Long Integer field (4
bytes) and nine Yes/No fields (two bytes)? or one Long Integer field (4 bytes)
and nine 255 byte Text fields?

It's simple arithmatic. Calculate the sum of the size of your ten fields (the
amount actually used; a 255 byte text field containing "XYZ" takes up only
three bytes). Multiply by 500,000. Is the result less than 2147483647? Betcha
it is.

In practice, I know of many databases with million-plus row tables. Aaron
Kempf will probably reply with his usual put-down of Jet, you may want to
google for his previous posts and responses to them and make your own
judgement.