what would be the best way to distribute the FE to my users outside of
email...

Rather than pushing updates, the general consensus seems to be to have the
user's machine do a version check against the "current" copy on the network
and pull down an update if needed. Details of exactly how to do that may
vary a bit.

Auto FE Updater
http://www.granite.ab.ca/access/autofe.htm

Even if you don't use his (free) tool, Tony's site provides a lot of good
ideas and links.

Nowadays I use a variation from one of those links
http://www.databasejournal.com/featu...le.php/3286111
because I ran into one client where .exe files aren't allowed on the network
(i.e., they are periodically deleted), so I couldn't use Tony's app.

--
HTH,
George


"Maldo" wrote in message
...
Thanks Chris for your advice. While on this topic, what would be the best
way to distribute the FE to my users outside of email. I would like to be
able to make sure that the users always have the most updated version of
the
FE on their local PC each time the submit their data.

"Chris O'C via AccessMonster.com" wrote:

Don't let everyone else share the same front end file. The most
important
reason for splitting the database and giving everyone their own copy of
the
front end is to avoid corrupted database files.

Chris
Microsoft MVP


Maldo wrote:
Chris,
Thanks for the repsone. It makes perfect sense. Sorry but I am new to
working with a split a database. I asked the user to put a copy of the
FE on
their local machine and everything works fine. Thanks again!!!

By having everyone share the same front end file, you defeat the
purpose of
splitting the database. Place a copy of the front end on every user's
PC

--
Message posted via http://www.accessmonster.com