Not that I'm aware of. You'd have to shell out to the other database. You can share Modules, but not forms.

You could make a 3rd "maintenance" front end for this.

Humm, the 3rd DB is worth considering as it will be used only by the system administrators.

You can add a reference to another database in the VBA Editor -> Tools -> References, then you can call all the public functions in that database (see picture below).  If that database has a public function that opens a form, then you can call that function to open that form.  And that is how you open a form in another database.  The caveat is that the form has to be designed and coded for use by two databases, which is a highly irregular practice.  This may work with unbound forms with few dependencies (e.g. message box form, etc.).  But those kinds of forms are usually simpler in design, so you may as well just copy it to another database.  Complex forms with lots of dependencies and references to tables, queries, etc. can almost always work with just one database, the one the form is created in.  To make it work with another DB, that DB likely has to be identical to the first DB.  So again, you might as well just copy the form over to the second DB.

This kind of "front-end sharing" concept doesn't exist in Access.  It is more in the domain of a client-server environment like ASP and web interface, which serves *everything* to the user, front ends as well as back ends.  In Access, the front end is always at the user's end.

There you go. Yeah, I usually used to put all of the admin features like that in a separate database. Instead of just making a separate admin menu, I would shell out to a different database. This way, the users didn't even have that code, and half the time they didn't have to be even connected to the admin tables.

Oh crap, I've just lost a day app development with all these posts and thinking about complex stuff I've somehow managed to avoid for ten years. All right everyone, back to work!