If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

how long is a piece of string? it depends on what you are storing in it as Teddy states.

You can stuff approximately 2GB of data in a JET database before it sulks (can't accept more data), it may explode long before that (become unusable due to size or other contatraints).

the precise calculation varies (depending on the number objects in the database, how well its maintained (AKA compact & repaired).

if you had one table with an approximate size of say 1Kb, then you would be able to store anywhere up to 2 million rows, if your row size was 1 byte then anywhere upto 2,000 million rows. This actual number would undoubtably be less than the theoretical as it will vary with the number of indexed columns, the number of forms / reports / queries also in the db. you are always going to loose some space for the system tables.

it also depends on table design, if you have a unique key (and if you don't then why not), then you are limited to the maximum number of unique values. if you use an autonumber as your unigue key then you are limited to the range of datatype long, wonder if the help system defines that? if you use say an 10 character alphanumeric then you have a maximum of 10 to the power of the number of characters your db can store - depends on the localisation of your db, if it supports UNICODE or standard ASCII characters. A standard ASCII character range is 128, UNICODE I forget. Not that I think JET still supports "ASCII only" though.

If you are really concerned then do some calculations, look at each table, work out the number of bytes per row in a table, multiply that by the number of expected rows per table, add some fudge factor to cover the indexes, unreclaimed space and working space needed to run (I like to use 100% as a fudge factor to allow for unforeseen "growth" in sizing a db [if I can get away with that is]) then add it all together, if it comes to more than 2GB then you have a problem.

In reality if you are concerned about breaking JET then you shouldn't be using JET as you data store in Access, switch to a server NOW if not earlier.

record count or 742,429
and 119,428 kb just compact it 115,724 kb now
growing by 500 to 900 records a days An the Computer does the data entry for me.

Last edited by myle; 12-13-05 at 21:46.

hope this help

StePhan McKillen
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment:Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010VB-NET based on my own environment started 2007SQL-2005 based on my own environment started 2008YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
DONT WORRY ABOUT THOSE WHO TALK BEHIND YOUR BACK
THEY'RE BEHIND YOU FOR A REASON