Thanks Dennison. Definitely something to look at for the next version.

Thus far, works like a charm. Have installed on approx 40 pcs thus far across 2010, 2013 and 2016 environments.

Awesome. Glad to hear it! I've had it running successfully in my office since about a month before I posted the videos online. I've got it running on 3 computers, rebooting once per hour, and have had ZERO glitches. Post updates maybe once or twice a week and they always go flawlessly. My previous attempt at a solution - trying to update just individual objects in the database - was too problematic. This one works a lot better.

Ok, so I spoke a little too soon. Still works like a charm but here's what occurred. I pushed an update. While the database was opening and the updater was running, I think the server version of the database, one of the users typed her username in the username textbox. The one that usually has Admin. The server version remained open with this username. When other persons momentarily opened the file, it read that an update was available, deleted and backed up the old version but could not upload the latest due to the non-admin account. I had to revisit all pcs and re-install. To resolve, I would lock or disable the textbox so this doesn't re-occur. So this is for future reference and a precautionary measure others can adopt.

Interesting. They shouldn't have been able to mess up ALL of the workstations, just the one they're on. Maybe lock that field and make the user have to double-click on it to change it? This is still very much version 1.0 software, so a lot of these little nuances still have to be fixed.