Hi Albert

IMO, the issue isn't really having two copies of the vcx (one in each exe), but that you only have one copy to work on.

By using a launcher app, you can make changes to the main system as well as to the reporting system. If you change any common vcxs, recompile both and store the new exes on the server.

The launcher app is run by each pc when they start the app. It looks at the exe on the server and compares it against the copy on the pc. If they don't match, the exe is copied to the PC and run.

This should reduce network traffic at startup and throughout the day.

It also means that for a particular group of people such as the managers, they can simply exit and restart their apps to get your latest changes.

Leave the report layouts excluded from the exe and let the launcher copy them to the PC too. You can do the same thing with particular vcxs.

You have to have the client restart to get the latest changes, by using the launcher you get the latest changes pushed to the client pc and drop network traffic to boot.



>Hi Mike,
>
>Could you explain with a bit more detail...thanks (no rush). I don't quite follow....
>
>Albert
>
>>Hi Albert
>>
>>I suggest you use a launcher. Build the reports .app as a new exe and use the launcher for both. When the managers run the reports exe, the launcher will send them the new exe with the correct subclass. I leave the reports out of the exe and have the launcher check and update them as well.
>>