Is the 2GB size limitation for a file or for the jet DB Engine?

[Mota]

Hi;
I have a growing mdb file that may reach to 2 Giga byte in the next few
months.Can i keep suspicious tables in a separate file,and be sure that
would not face to the size limitation problem in the future?In this case i
have to use that tables thru this method:
Set DB=OpenDataBase("DBfullPath"),and search them thru Find method of DAO
recordsets,without linking to them.
In fact,if the limitation is just for a file,this must solve my problem.But
if it pertains to the Access itself or Microsoft Jet DBEngine,i dont know
what to do.
Do you have any better comments other than avoiding big tables? (for we need
to collect that data)
Thank you for your help.

 

[Bill Edwards]

Split the front end and the back end.
Divide the back end tables across multiple mdb files
Link the data from the multiple mdb data files to the front end.

or

Change the back end to SQL Server

 

[Marshall Barton]

I have a growing mdb file that may reach to 2 Giga byte in the next few
months.Can i keep suspicious tables in a separate file,and be sure that
would not face to the size limitation problem in the future?In this case i
have to use that tables thru this method:
Set DB=OpenDataBase("DBfullPath"),and search them thru Find method of DAO
recordsets,without linking to them.
In fact,if the limitation is just for a file,this must solve my problem.But
if it pertains to the Access itself or Microsoft Jet DBEngine,i dont know
what to do.
Do you have any better comments other than avoiding big tables? (for we need
to collect that data)

You should split the database into a front end with
everything except the table and a back end with just the
tables. The fron end then links to the tables using the
Linked Table Manager (Tools - Database Utilities menu).

When the back end gets too big, you can move some of the
table to a second back end. The only significant drawback
to multiple back ends is that you can not set Referential
Integrity between table in different database files.

 

[Jeff Boyce]

That's a fairly large database. Do you simply have a very large volume of
data, or is your database suffering "bloat"?

Are you keeping images in the database? Have you backed up your database
and then run "Compact & Repair"?