Most software development platforms split the data (tables) from the application (forms, reports, etc.)
The benefit of splitting a database is primarily to allow the application to be used efficiently by more than one user on a network.
I do agree that in a multi user environment that you must not share a database so that means it must be split.
IMHO, the reason you split the database is because it make development easier and also protests your data. This has nothing to do with the number of users. To me it is able "best practices" for software development and data integrity.
The dis-advantage of being split (only one):
The only thing that might seam like a disadvantage to splitting your database is that if you want to make table design changes, you have to open the back end. Thats is it!
Some of the advantages of being split:
1) protects the data. Can't make table design changes from the front end. If or when the front end gets corrupted, it does not corrupt the data.
2) can use a MDE/accde as the front end to protect the app.
3) can easily deploy updates (just replace the front end)
4) can easily link to test data while developing, then switch back to the real data when ready to deploy an update.
5) back ups are smaller since you only need to back up the back end (data) regularly
and also do not forget:
6) the database is multi user: each user can have there own copy of the front end so it is not shared. You can even have multiple versions of the front end for different versions of Access that can be used at the same time.
As you can see, most of the advantages have nothing to do with being multi-user.
I start out every database split. I will not work on any database that is not split. Why? see the above list of advantages for a start.
Also see:
Auto FE Updater
Windows Vista now supported.
- Starting an exe, such as the Sagekey runtime system, is now supported.
- Fixed the "The MDW account name and password in the INI file weren't valid for
opening the MDB to determine the version of the MDB" message when in a mixed
operating system work station environment.
- Emphasized using %appdata% as a location for the Front End MDB/MDE in the sample
ini files and documentation
- added error numbers to the messages. It was getting a bit difficult tracking down
specific error messages in the code.