The correct way to deploy an Access application is to use the database
splitter (Tools, Database Utilities, Database Splitter). It creates two mdb
files. One will retain the name of the mdb you started with. It will
contain all your forms, reports, queries, macros, and modules. It is
commonly referred to as the Front End (fe). The other file will have _be
appended to the file name and will contain all your tables, indexes and
relationships. It is commonly referred to as the Back End (be). It should
contain only data. Do not be tempted to put other things in it.
The be should be on a shared folder where all users have read, write, and
delete permissions.
Each user should have a copy of the fe on his own computer. It also should
be an mde file. It is not a good idea to deploy mdb files to the user.
The fe "links" to the tables in the be. A word about that. Since in many
cases not all users will have the same drive mapping. It is best to use UNC
path names when prompted for the location to put the back end file. A UNC
path name uses the sever name and folder path rather than a drive letter. It
will be something like \\ServerName\SomeFolder\SomSubFolder\MyApp_be.mdb.
That way, it will not matter how a user has their drives mapped.
As to making changes.
If you make any changes to the application (fe), all you need to do is to
deliver a new copy of the fe to the users.
If you make changes to the tables (be), it takes a bit more work. You have
to choose a time when you can have be be opened in exclusive mode so no users
can use it. You can then import any files you created in your test version
and select definition only when you import them. If you have made changes to
existing tables, you can open the table in design mode and make the changes.
Once you have made your changes, it is a good idea to do a compact and repair.