Maximum Size for Tables

[Chuter]

I am involved in a archiving project that will require backing up historical data from mainframe system tables.....some of which are huge (1 Million plus records and up to 100 fields). Just looking for some feedback that I can use in evaluating Access as a suitable back-end. I know there is a "theortical" limit of 1 Gig for a table, but am curious to hear some comments on a table's "practial" limit..ie at what point do things become unstable and/or performance really suffers.

 

[LittleSmudge]

It depends more on your implementation.

If you have a network resident Back End datastore and distributed FrontEnd user interfaces then if you don't do anything special you will heavily load the network bandwidth.

If you bind a form to the large table simply by placing the table name in the form's Record Source then when you open the form the ENTIRE table contents will be transfered over the network before the first record is displayed.

Solution is to use ADO an just get the one record that you need and populate unbound controls on an unbound form.


G LS

 

[Chuter]

Thanks for your input and ideas!

 

[yowza]

I am also interested in the 1gb size limitation. We are using a product called Maxware to push/pull data and it uses Access for the DB. We exceeded the 1gb and it froze up our system. The folks using the product ended up using two DBs instead of one as a temporary solution. The perplexing thing is that there is another one of our customers who have successfully exceeded the 1gb with no problems. As you may have noticed, I am new to the Access area and have not had a chance to work on this part of our project yet. Any ideas or suggestions would be greatly appreciated.

Thanks,
yowza