Need help understanding record limits for input tables

[bomstadmk]

I'm trying to understand the limitation on a data table. The on-line help describes it as being 2 gb. Is that truly the only limitation or is there an underlying record limit as well? Unfortunately, the data that we're pulling in from a PLC comes one line per tag even though all (20 in this case) tags are associated with one record.



Any help in understanding this would be appreciated as the scale up difference is orders of magnitude different on the information that we can store.

[pbaldy]

The limit on the overall size of the database is 2gb; the limit on an individual table is 1gb. Look up "specifications" in help for more info.

[NTC]

there is a width limitation of 2000 bytes in a record. this can be handled by making 1:1 tables however.

[wilpeter]

Would you tell me where I can check the current size of one of my tables that has 65,000 multi-column records. Although the program doesn't slow, it seems prudent to archive transactions that are up to 10 years old...any suggestions?

[Renaud]

I do not think there are any easy tools to tell you the size of the data contained in a specific row, column or table in a database.
What you can do though is simply make a backup of the database, open it and delete all other tables then compact the database through the Compact & Repair menu in Access.
You will end up with a database of the size of that specific table.

I have to say though, that unless your database is already huge, 65,000 records is not that much.
Just make backups (always make regular backups!) and worry about archiving when performance or size are really becoming a problem.
Compact your database regularly to keep its size in check too.

[wilpeter]

Yes, thank you for that advice. Turns out it is barely 13 mb. I guess it's just that when I started with computers, back in the 80's, space was still a concern and compacting took several seconds. Now the setting is to compact on close and to back up each month and it just seems miraculous that it takes a second to alphabetize a non-indexed column of 65,000 records! My apologies to the industry for doubting.