Separation of make tables and tables and queries?

[Access9001]

Under Access 2003, what is a good way to separate this?

My initial idea:

MakeTable.mdb, which creates multiple large tables and stores them in:

DataStorage1.mdb

And checks the size of each mdb as it does so. If DS1 gets too big, then it will create and start storing the tables in DataStorage2.mdb and so forth.

Then we have:

QueriesAndLinks.mdb, which link-tables to every table as located in DS1, DS2, DS3, etc, with all relevant output queries/views.

Is this a wise way to arrange it?

 

[ghudson]

Are you compacting the database? If you have to archive the data then you might consider moving the records to an archive database if you want to keep the productionn database with only the current data. Moving would involve appending the records from the production database to the arcive database then you would delete the records in the production database.

 

[Access9001]

Yes I am compacting the database. I am just trying to separate everything into a proper reporting structure in terms of frontend/backend/utilities for exporting/queries/etc. The data I deal with is massive, and so make-table queries in one database aren't possible (the data exceeds two gigs easy).