You can do anything you want. No need to justify your solution.
All we're saying is it is safer to open a "launcher" than to open the actual database and have to close it to overwrite it, not to mention the "overwrite" being more complex. The "launcher" also allows you to always download a new version if that is desirable. Everything happens behind the scenes. The user isn't notified since he has no choice. The app decides what to do based on the version compare. Allowing people to ignore an update doesn't sound like a good solution.
PS, the "launcher" has two version tables. One linked to the local FE and the other to the BE.
As I mentioned, the update is on the Web, not on a local network. If there is no connection to the Internet, then obviously no update can take place, but if there is, the user is not asked to allow the update.
The launcher db is cleaner, but it is a second db.
Also, with a launcher db, the user would not immediately see the application he is using. The launcher db script/db would work very well in a local network setting.
