General information
Category:
ActiveX controls in VFP
Title:
Registering ocx fails
Environment versions
Network:
Windows Server 2008 R2
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
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only