Thank you John for your reply.

You're right, information is needed.

Let's start with the concerns you raise.

The application is "installed" on each machine; Actually how we work is this way; There are several applications - the same modules that are separated into different folders. Each one contains its executable and its pbd's.
In another different folder we have all the DLL's (runtime), and when we run the initial application (menu) it starts in the folder where the DLL's are located.

We are working with computers with Windows7, Windows10 and Windows11.

When an update is released, the executable and the PBD's are copied to their respective folder (this is on a server); and through a third-party program; We update each of the workstations.

Every time an update is made, we ask users to exit the executable and re-enter

Hope this was usefull.

Regards.

Hi, Mario -

You'll need to provide some additional information. We are not sitting alongside of you at your desk, so you need to be much more descriptive of your environment/setup/processes. You have not given us any useful information on which to base any suggestions. For example:

Is the app installed locally on each machine or on a network-accessible drive/folder?

What is the process that occurs when "an update has been released from development"?

Typically, when a new set of app PBD's/DLL's is made accessible (installed), each user must exit the app and restart it. Is this occurring?

Best regards, John