I wouldn't use that "tip". There is no advantage to it since the runtime is freely available and as with all "tips" of this type, you run the risk of MS doing something you didn't expect.
I use a batch file to distribute new copies of the FE to each user. So to add a new user, someone sends him a shortcut to place on his desktop. The shortcut runs the bat file which remains on the server. Using this method, each time the user runs the shortcut, a new copy of the FE is downloaded and replaces the old copy. This gives you a pretty flexible environment. You should avoid distributing updates during working hours whenever possible but in an emergency, you can send an email to all your users asking them to shut down and reopen the app. You can carry this further if you have a need and use tables in the BE that are checked regularly to control forcing a shut down. But first things first. Here is the .bat file I use:
md c:\DwgLog
del c:\DwgLog\DrawingLog.accdb
copy "\\BSCCTIMBERLINE1\Timberline Office\AccessApps\Data\CommonFE\DrawingLog.accdb" c:\DwgLog
c:\DwgLog\DrawingLog.accdb
Change the file and directory names to suit your app.
Here is the Citrix version of the file if you are using Citrix for any users:
md %USERPROFILE%\DwgLog
del %USERPROFILE%\DwgLog\DrawingLog.accdb
copy "\\BSCCTIMBERLINE1\Timberline Office\AccessApps\Data\CommonFE\DrawingLog.accdb" %USERPROFILE%\DwgLog
%USERPROFILE%\DwgLog\DrawingLog.accdb
As you can see, for this client I distribute the .accdb. These users are all professionals and are not inclined to break in to the app but if you prefer, you can compile the app to .accde and when I do that, I rename the app from .accde to .accdr because the .accde still allows the user to modify tables, queries, and macros if he is using a full version of Access so it doesn't provide much protection. You can also rename the .accdb to .accdr. Access doesn't really care what extension you use but the .accdr extension adds some additional protection in that it forces whatever version of Access that opens the app to operate in runtime mode. That means that you cannot put ANY object into design mode while the file is named this way. The user would have to be aware that he needs to rename from .accdr back to .accdb in order to get to design view on any object. Remember the .accdr trick is not real protection but if you dont' tell your user how to get around it, they are unlikely to work it out.