views:

8

answers:

0

At a customer's site I have an .EXE sitting on a server share which is accessed via a mapped drive on all user machines. (Yes, I know there should be an MSI which would distribute the application but I am stuck with how it is at present.)

Sometimes there are some issues with OCXs that stop working on a user machine if I upgrade the .EXE on the server. My solution has been to un-register and register the OCX on each user machine, however this requires administrator access and this is very difficult to organise if there 15+ machines.

Is there a sure way to upgrade the .EXE on the server while avoiding the problems with the OCXs? Would Registration-Free COM be a solution for this?