Splitting my database

[browninaz]

Hello everyone,

I split my database, _fe and _be, and have a few questions. I have been told by a gentleman in this forum that my .accdb files should not exceed 2Gb each. I have 20 or so tables, and at the rate that we are inputting data, it is filling up quickly. I would have to guess that I will be at my limit in 2 years, maybe less, and was wondering if I can split my tables into individual files and link my _fe to each individual file. Does anyone think that would cause a problem? I'm trying to avoid SQL server or any other type of back end for now because for one, I am going at this alone, and two, the cost. I think that by the time that I run out of room, I'll have the knowledge I need to move forward with alternate _be storage.

Thanks to all who know more than me...

 

[plog]

Yes, you can split your backend into multiple files without too much trouble. But, why solve a problem you don't have?

Compact and repair your database today, see how big the thing is. Do it again in 6 months, then again in a year. Then calculate when you think the thing is going to go over 2GB and fix it 6 months prior to that. 2 years is a long time. Maybe you'll get a new version of Access with larger size limits. Maybe IT will move it to a different platform. Maybe the whole thing will be obsolete. Don't waste your time worrying about the things that might be problems so far down the road.

 

[NeutronFlux]

Just a note about costs, you can use SQL Server Express for free. I believe newer versions allow 10GB per database. It takes more more knowledge and work to setup, but if you have very large recordsets (properly indexed and queried) or you're accessing your database over the network, you may be able to achieve serious gains in performance. It might be something worth spending an hour playing around with.