I’ve decided that I’m not going to do this at the moment due to time constraints and other important features needing to be added to the database, but here’s what I’ll do eventually.

I have one mammoth import database with one table for a file list and three more tables storing data processed from those files. The other components of the application suite are other access programs that generally all use the file table, but only one of the data tables.

The plan is to split those data tables out to their own individual files. This gives more space for each table to reach the Access file maximum on it’s own. Right now, the single file is reaching it’s maximum size after processing about 6 months of data. By my calculations they should be ablet to go a year or more if I split the tables into their own individual files.

It’s not too hard really, but I can’t do this while the system is being used. So I’ll wait until an evening when everyone is out, copy the data to multiple files, and re-program my front ends to connect to the new files with the same data. The users won’t notice anything has changed from their end, the apps will simply be linking to more backend files.

Easy Peasy.