Check for repairDb,  this utility is for remote distribution of databases
http://www.sayger.com/demos/repairdb/repairdb.htm

best regards!

You should have the application split into a front-end (containing the
queries, forms, reports, macros and modules), linked to a back-end
(containing just the data). In that way, you simply give them a new
front-end, they overwrite the existing front-end with the new one, and
you're done.

Make sure you add code in your front-end to be able to relink to the
back-end. There's one approach to this in
http://www.mvps.org/access/tables/tbl0009.htm at "The Access Web"

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele

You should, of course, have split the database into a front-end (queries,
forms, reports, macros, modules, and perhaps local lookup tables) and back
end (tables, relationships, and the data).

You keep a copy of the front end and a test-data copy of the back end for
developing changes. Link the tables using the Linked Table Manager or code
that you'll find in the Solutions sample database (for Access 2000 and
later, download from
http://msdn.microsoft.com/library/en-us/bapp2000/html/bap2000.exe, for
Access 97 and earlier, look on your installation CD if you don't find
"solutions.mdb" with a Find or Search. That way, you can modify the front
end and just send them a new copy -- at most, they will use a form to link
to the data tables.

You didn't say whether this was single-user or multi-user, but this approach
works nicely for either one, and I'd assume it is multiuser, given that you
posted the question here. Visit MVP Tony Toews' site
http://www.granite.ab.ca/accsmstr.htm for the best collection of links and
info that I've found on muliuser performance and corruption avoidance. He
even has a freebie for distributing updates.

 Larry Linson
 Microsoft Access MVP

Many thanks to all of you for responding.  Your input is greatly appreciated
and will save me quite a bit of time and headaches!