So far no issues for me.  They both work soooooo nice!

Question. Since I have both the Updater and Backup DBs and my database is split, and I have my FE (copy that gets updated) and BE in the same folder on another server, would it make sense to  have the BackupDatabase as a separate DB altogether, always open on my (the developers) computer?  
That way I would only have one FE to work from and not have to manage to FEs, one with the back up form and one without that would be for updates.  The FE on all DBs would close and the BackupDatabase would be able to to its work.
Does that make sense?

Yeah, whatever works for you is good. Honestly, you really only need to backup your BE file for the data. As long as your FE file that you're developing on is sitting on a drive that gets backed up (like I use Google Sync) then your changes will get saved in the Cloud. Google keeps versions too.

At about 18:40 on the Automated Backups video, you talk about placing a docmd.quit on the main form.  This is in case anyone closes the main form it will close the database down.  I've tried it on the On Unload and On Close events but both give an Run-Time error '2046':  The command or action 'Quit' isn't available now.
Can you help?

Do you have anything else running live/bound on the main form? It works fine for me on the on close event. You could also try to save or do a If Me.Dirty = True Then Me.Dirty = False before you run the quit command and see if it works.

You should literally just be able to put "Quit" in the On Close event and if the form is closed, the whole database shuts down. Like Adam said, if you have any other events running or something happening in the background, that could interfere with it.

Not sure why but I'm still not getting that to work.  Same error.  The main form is not bound.  It does have some commend buttons on it. It also has a few text boxes the populate via DCount and Date() and Time().  So I deleted eveything on the form...still the error.  Then I created a new database with one form.  Input a On Close event to the form or 'Docmd.Quit'.
Still the error.  "Run-Time error '2046':  The command or action 'Quit' isn't available now."
What am I doing wrong?

The fact that it errors on a completely empty database with just a form and button is odd.

Just to confirm, is the database running in a trusted location? (Both your real one and the test button one)

Try opening the database Exclusively. See if it works then. If so, it's a problem with another user (or instance) connecting to your database.

What version of Access? I know there were some bugs in older versions like 2010 causing problems with Quit. Update to the most recent version.

And of course, I know you've already tried running down the Troubleshooter.

Also, try Application.Quit instead of DoCmd.Quit. See if that works.

It is not in a trusted location.  It appears that I cannot add a trusted location probably due to the IT rules here.  Not sure.  Would that be the cause?

Yes, absolutely. If the database isn't running from a trusted folder, MOST "potentially unsafe" functions and commands won't work. To do any serious development with Access, you'll need that trusted folder.