Split Your Database

Simple Security too

User Level Security 1

I read your question as you mean to split the database into multiple databases for each warehouse.

Another option is just to design the front end with that in mind. You could just give different front ends to the different warehouses that are filtered to only show their data.

Ideally you would use a solution like login information like Rick linked to control all of that so you wouldn't have to have multiple front ends.

If you're interested in dividing a database across multiple locations, there are several methods you could employ. One simple way would be to create a copy of a database file and distribute it to the various locations, assuming they'll all be managing their own distinct sets of data.

In this case, I would recommend splitting the database into a front end and a back end. This allows you to make design changes to the front end without disturbing their back end data. When updates are required, you simply send the new front-end file, sparing the back end unless table modifications are necessary.

However, if your goal is to have everyone working off the same database with a shared dataset - like a common customer list - I would direct you to explore options for using Access online. This could provide the unified solution you're looking for.

Access Online

Thank you, guys, for all the assistance. I will start exploring those options, thanks again for your time!