The other question is where the front-end resides.
In our site, the developer / owner / maintainer of the files places the Back End (BE) file on the shared area. Then as a separate act, do the linking via UNC mapping. Then as a third separate act, place the Front End (FE) file on the shared area.
Now each user COPIES the UNC remapped FE from the shared area to their individual workstations. As long as everyone has appropriate network permissions, this will work.
Note that there can be more to it than I just stated. Search this forum for the subject of FE/BE Split with those terms abbreviated, expanded, etc. Also look for Split Database.
Doing this "right" isn't always easy. It can in fact be quite tedious.
One last thing to remember. If you did something to compile, lock, or otherwise protect the file, the shared FE is NEVER the one you update when making changes. In all cases, you keep a local copy, muddle with that, and then when about to publish, make a copy of the master copy, do your compile / lock / protect steps on the staging copy. Keep that one private copy as the master and keep it inviolate. NEVER EVER IN A GAZILLION years would you ever directly muck the shared FE copy.