To split or not to split

[vent]

Hi everyone

So I've learned recently that splitting the database onto a "live" and "dev" version is beneficial since its more secure and the user interface would be easy to modify. I'm considering doing this but first I would like a little more info. I'm presently the only one working on it, the goal of this database is pretty simple as it's going to be used to track important information pertaining to educational programs used for student internships. This includes companies with a partnership with the collegiate and their info (e.g. address, email, insurance info, etc). Prior to this, I've just been making backup copies daily and using a changelog and keeping track of changes I've made. At the end of each week I do a compact & repair. That being said, since I'm the only one working on this, should I bother splitting the database or continue to backup regularly. Is there other reasons why I should or should not split the database. Thank you.

 

[pbaldy]

If you're the only user and that's the way it's going to stay, then I suppose you could leave it alone. If anybody else is going to use it, I'd split it. The only app I've ever built that isn't split is one I use to keep track of computer equipment. I'd operate on a "when it doubt, split it" philosophy.

 

[The_Doc_Man]

Concur with Paul. Splitting a DB into FE/BE (so that you can have multiple FE) is done when you are SHARING the database. It is a methodology to avoid file locks and database component locks. If you aren't sharing, those locks are only your own anyway, so splitting is probably not an issue. HOWEVER, frequent backups before embarking on each change or maintenance cycle is probably an incredibly important issue.

 

[daniel.smith.10]

Some reasons to split an Access database
1. Multiple users share the data
2. Data is better protected
3. User interface is easy to modify
4. Can use a shared security model
5. Multiple developers can work more effectively
6. Corruption is limited