I'm very shortly going to be writing a routine which, when the user
clicks on the appropriate command button, hits my website and
downloads the updates, unzips it and puts it into place.  Of course I
also have to get this going with the Auto FE Updater so it's not that
simple.

Just thinking out loud here.

Tony

No packaging nor uninstall is required. You strictly overwrite the
front-end.

While Tony mentioned an update he's planning for his free Auto FE utility,
what he currently has should be sufficient for your needs. Take a look at
http://www.granite.ab.ca/access/autofe.htm

Don't use the packaging wizard for updates. It simply isn't designed for it
(Over the years, I've had so little luck getting it to do anything well, I'm
tempted to insert some pot shots about what it is actually designed to do,
but I won't.).

Either:
1) have an update strategy pre-built into the app. When opened, the app
checks for new fe on the network, copying it to local if found.
http://www.databasejournal.com/features/msaccess/article.php/3286111
outlines a basic approach.

2) use a tool like Tony Toews' Auto FE Updater. A process similar to the
above, but utilizes an external exe and users *have* to use your shortcuts
to open the app or they'll bypass the file check)
http://www.granite.ab.ca/access/autofe.htm

There are multiple variations of #1 and #2

3) use a real installer (like the free Inno setup) to distribute an
executable that contains just the update.
http://www.jrsoftware.org/isinfo.php