Splitting The Database

[adams.bria]

So here is what I am thinking about doing, I just want to know if

a) it is feasible
b) anyone has done it that can tell me whether I'm going down the wrong path

So I have one set of demographic data. However, for many of these people they are involved in 3 programs (A,B,C). Sometimes one might just be in two of these programs, or even one. 10-15 surveys per year are required for each program, and each involve about 3000 individuals (for a max total of around 4.5-5k individuals). When I split the database can I make 3 front-ends, one for each program, and have each one link to the back-end? Obviously each one would connect with different tables, but as long as the necessary tables are linked it should work (at least that what my mind is telling me).

Well before I go to far with this idea I wanted to spit it out here first and hear some ideas. Thanks guys!

 

[CBrighton]

It's possible, yes. You can link as many databases to tables in as many databases as you want (barring any universal limts like database file size, number of objects in a single file, etc).

However I would only do it if the data is reported on together.

With the limited number or connections advised by Microsoft for Access databases I'd have 3 backends unless they needed to be together. Any downtime or corruption will have less impact that way.