Another disadvantage is that if you are going to change the design of your BE, you need to ensure that nobody is accessing the data. It may then be necessary to update everyones FE to work with the new BE design.
hth
Chris
I solved that a few years ago, by having everyone load the database via a batch file on their desdtop. Works real well.
The batch file loads a fresh copy off the network to the d:\service directory and then runs the database frontend from there. The system.mdw still resides on the network along with the backend.
I have some nice "kick" routines if it is necassary to get everyone out of the backend. If I release a new front end code base, I just put it on the network and the next time anybody exit and re-loads the database they always get the latest code base. If I need to force them to exit and reload, I have that built in via a message table that the main menu checks every five minuted. If a message exists telling them to exit, they get a warning to save what they are doing and then within another 5 minutes, the database shuts down automatcially for them and they have to re-load it via the desktop batch file. For the majority of users, they don't even understand that it is a batch file. They just double-click it and within 10 seconds more or less the database it running in front of their eyes.