Keeping your FE and BE on the same machine for each user implies multiple ACTIVE copies of the BE which implies DIVERGENCE of the BE from each other starting from that point in time at which you made the copies. There are ways to reconcile multiple divergent databases but they add to your overhead a LOT. The term used for this case is "synchronize" when applied to Access databases, and that is another topic to look up.
You claim to be inexperienced (and we have to trust you on that.) You need to trust US when we say that keeping copies of the BE on multiple machines will lead to serious headaches and sleep deprivation, growing worse in direct proportion to the number BE files to be maintained.
My best advice is to "sacrifice" a machine to become the "server" for the BE file. Remember, if you are using Access, it only has to be a passive file server, not something more active like SQL or ORACLE servers. This machine can be used for other things perhaps, but the key is that it can never be turned off during the hours during which your user base wants to get into the database application. "Sacrifice" also because you will have to "appease the Access gods" by backing up this machine (or at least the shared folder holding the BE file) on a VERY regular basis, to the point of being nearly a ritual. You will need to do other maintenance on this machine during lulls in your business -perhaps during an off-hours maintenance period. At least the Access gods don't require sacrificing a virgin every so often.
You can also keep the current, most recently released/updated copy of the FE on that same machine but it would be a REALLY good idea to determine that system's name and add code to the FE file to stop it from running directly on that system. If you have an opening form, the .FormOpen routine of that form is a good place for the test. If you catch a user directly running the FE from the shared machine, some serious knuckle-slapping with a hard ruler would be a good idea.
There is a techie reason for all of this. By putting the FE on each user's machine with the queries, forms, reports, macros, and modules in the FE, you prevent the case where two users opening the same FE file from the same server at the same time incur some type of file locking interference. If the tables on the BE are shared but everything else is in the FE and NOT shared, you have eliminated file locking issues for everything in the FE. If you then use OPTIMISTIC LOCKING (look up that help topic), you further reduce the frequency of BE locking. You can never truly eliminate it, but you can reduce the heck out of it. This is a good thing to reduce.