The updater doesn't do anything with the tables. You're just pushing the FE out.

And it works great, I use mine in this way. When I want to push  out a new update I just use my ACCDB file to save as ACCDE, overwrite the file that I'm updating, and then after it saves, it opens as an ACCDE and you push out the update then.

^^^ What Adam said. :)

Perfect!  Both the Updater and BackUp DBs are awesome.
Great product Richard.

I'm glad you like them. I honestly wish I had something like my Access Updater 27 years ago. I had one client that had 15 workstations. Every time I made an update to his database, I had to run around and install new FE files everywhere. The worst part was waiting for Karen to get off her computer because she was playing Minesweeper - er - I mean updating her customer accounts.

LOL, we all know Karen

Adam,
A couple of questions:
1.  How do you handle the Access Updater DB v. number with the scenario you described above?  If you use your ACCDB to save as ACCDE and then push out the update from the ACCDE, the ACCDE file version number increases by one, but the ACCDB version number stays the same.  So when you use the ACCDB file to make changes and then follow the sequence above, your version number on the updated ACCDE will stay the same.  Maybe I'm misunderstanding something.  

2.  I'm also using the BackUp database from Richard to back up my DBs.  I have multiple DBs to back up, but since it will not back up subfolders, I'm placing the back ends and the copy of the front end, in one folder on the server.  The Backup Database then works great to create a back up.  But now, I'm attempting to use one AccessUpdater.accdb for two or more databases in that same folder.  It looks like it works but, any issues doing that?
One issue is the AccessUpdater.LOG does not distinguish between DBs

1. I don't believe your master DB changes numbers, at least I haven't seen it. However, the ACCDE you're going to create will change numbers. I'm up to around 100 already. When you save your master ACCDB copy as a ACCDE file or overwrite the previous one and push it out from that ACCDE, All that is done in the DoVersioning sub of the access updater I believe if you want to see how it's working. It's in the log file.

2. Couldn't answer you on this one, I don't use the backup template or the updater for 2 databases in the same folder. If you've investigated it and it looks like it's working, then you're probably good to go.

When I save a newly revised developer FE (ACCDB) as a ACCDE overwriting the previous ACCDE, it sets the version back to the one of the ACCDB.  How are you getting around that?  
For instance, my ACCDB shows Access Updater DB v.28.  I hit Save As and the ACCDE and overwrite the existing ACCDE.  Now the ACCDE shows Access Updater DB v.28.  I then push an update with the ACCDE and the version changes to Access Updater DB v.29.  Good!  But then I do another update to the ACCDB and again hit Save As / ACCCDE and overwrite the existing ACCDE.  Now the ACCDE is once again shows, Access Updater DB v.28.   This is where I'm stuck.
The only way around it that I've found would be to go into the ACCDB file/options/current database and manually change the Application Title prior to saving it as a ACCDE.  Thoughts on that?

My ACCDB doesn't even have an access updater version, it just says Access.  Maybe a difference in settings?

You have the remote DB set to the ACCDE and the local db set to the ACCDB on your main PC your pushing updates out on?

I'm going to be adding options to automatically compact/repair and make ACCDE files to the next version of the Updater. Hang tight guys.