The code in question tries to run as FoxFire is an "add-in" so it attempts an install when it is launched from within a custom app (i.e. my app). But it is very old. I have not yet tried to install the .ocx manually yet as looking at their code, it seems like it is not just a "regsvr /ocxfile" situation. I guess I will have to wait for their tech support.

Thanks.
Albert

>Typically installation of components of OCX should only be performed at install time rather than the application -- IIRC enforcement of this restriction started with the much-maligned Vista. A one-time workaround in this situation is to launch the application with the "Run as Administrator" option (not run program while logged in as administrator, but right-click on icon, then select from context menu "Run as Administrator") -- then perform the action that would've installed the OCX (where it will likely succeed), then exit. Hopefully the code in question is smart enough not to try reinstalling the component and the program will run normally after this point.
>
>>Hi all,
>>
>>Have not dug into this in depth but just got a call from a user and they are switching a VFP app to new Win 10 machines. When they fire up their report writer - Foxfire, older ver 6, it tries to register actbar.ocx (1999 vintage). It fails. I am not onsite yet to try it (and my current OS is 8.1).
>>
>>Should the program code (in Foxfire) be able to register this component or is Win 10 just that much more restrictive? I know the old "manual" way to register it was via RegSvr32 actbar.ocx. I don't have the source code for Foxfire to know what it's trying to do. Thought I would ask first before a lot of work just to find out Win 10 is blocking.
>>
>>Thanks,
>>
>>Albert Gostick