Ok. Assuming you don't have any Access tables, just Sharepoint linked tables, then , as others mentioned, you want to consider your database file a "front end". (we sometimes talk about FE and BE, but there is no back end access file in this case, because there are no access tables - if there were, then you would put all the tables - and only tables - in the BE and retain a single copy of that on a network folder, with each FE linked tables to that single BE).
Give all your users a copy of the front end. They should use it from their local machine. Start > Run > %appdata% is one place that often works well for me to put files like this - maybe in their own subfolder, with a desktop shortcut or something.
As soon as you begin this "distributed FE" method, the next thing you're going to want right away -- or maybe do this before distributing them -- is a fully automated
versioning/version distribution system. This means you want a method whereby, each time you make a change to your private "master" development copy of the FE, and place that copy somewhere out in an obscure network folder, ALL of your users automatically GET a copy of that updated FE--without either you or them having to do anything.
Because who knows - sometimes you may need to make changes weekly, daily, or even more often, depending on what happens. The last thing you want is to have to email each person all of these files...etc. An auto version distribution system empowers you to continually improve and respond to requests re: the database without any sweat.
This sounds much harder than it is...See
here for some ideas, & review the whole thread for more.
In my opinion, don't move to the fully-distributed-front-ends approach until you've solved for auto versioning, else you'll just have created an un-maintainable scenario. And use Gasman's suggestion for accde/locked. Another solution that might feel easier if you want is to just change the extension from accdb to accdr. Doing this forces the database to open in Runtime (100% locked down). Two things to understand IF you just change the extension to
accdr.
1) People
could just change it back to accdb if they were that knowledgeable and curious. One more reason to give them a desktop
shortcut, rather than putting the file on their desktop--"security by obscurity", as is often the case with Access.
2) Any time your code produces an unhandled error, like a runtime error, say, "Type Mismatch"--and if you don't have an error handler--the application will shut down. This may be true in accde too...I'm not sure, because I always have error handlers in code procedures.
HTH