Here is how I've done it in the past.

Program files are stored on a network drive that is available to everyone. In our case it was the K drive with the following folders:

K:\PBApps\Appname

K:\PBApps\Appname\version1

K:\PBApps\Appname\version2

The two version folders have copies of the exe & pbd files.

The Appname folder has a .bat file that launches the application from one of the version folders, the one that is current. The shortcut on end users desktop points to the .bat file.

So if version1 is current, I would copy the new exe into version2 and then modify the .bat file to point to version2. Then I would send an email to all users letting them know that they need to logout and back in to pick up a new version.

At a previous employer we used a program which was a windowless app that read a .ini file to determine which version folder to launch the app from. The advantage to that approach was that it had the same program icon making shortcut creation easier.

Hi Ian;

  FYI: Once an object is referenced from a PBD, it's "definition" is cached in the "Class Pool" memory buffer of the PBVM. If your App references that same object class again, the PB Loader checks the Class Pool first and will always take the definition from there before searching a PBD.

Regards ... Chris

you need to restart the application.

I believe the pbd itself isn't loaded, but the objects that are used are loaded into memory.  

What we do is check for updates, copy them to the local machine, then restart the application using the user's login information via commandline