Now that you have the idea, maybe I should not dare add my comment.
The FE (Front End) and BE (Back End) are very necessary. The BE can be an Access dB, SQL Server, or other type of database. Access or SQL Server (any level) are great choices in my book. You will want one copy of this for all the FE to link to one way or another.
Then make the FE into a .mde as you said. In general, this keeps users from having access to your code among other security controls.
For distribution:
You will have better response and more consistant response if you can give each user thier own copy of the FE. If you put one FE on a network drive and have everyone try to share it, there will be resource issues. Ideally, each person is somehow distributed their own copy of the MDE that connects back to the single BE database file.
At one site, I use a 3rd party software that distributes the FE to each users's PC every time a version update is released.
At another site, I use Citrix Services to create a custom folder each time a user loggs in and the server copies the latest versionof the FE into that user's folder during the session.
Hope that helps! I am leaving on vacation in 30 minutes. And will have many drinks while fishing from the back portch.