Hi Rich,

Thanks for your response. I'm excited by Christan's discovery of a technique for avoiding ActiveX registration on XP and 2003 and by your confirmation of this technique. I'm going to experiment with this solution to see if it will provide us with some additional flexibility for working with ActiveX components.

Regards,
Malcolm

Malcolm,

I already documented up the XML Manifest File solution in the Help File. I haven't posted any updates with that information yet. But, it will be in the next update. It works well under XP. I did not test it under 2003 Server.

I tested it in several scenarios. I unregistered my control from my system completely and then created a vfp9.exe.manifest file and started VFP 9 with an older version of the control. Then, I registered my latest version of the control again in a different folder using REGSVR32 and VFP 9 still loaded the one from the manifest file correctly. Then I started VFP 8 and loaded the control and it used the version of the control from the system registry. So, it appears to work quite well. So, this appears to be a very good work around for those "locked down" machines. I will also include a sample manifest file in the new builds as well and all that needs to be done is to copy it and name it the same as your application.exe with the manifest extension.