Eric,
I wish I could just put it into the local folder. However, ActiveX controls don't work that way.
I have unregistered the control, and registered the control after, restarted, uninstalled Symantec Endpoint and tried it all again. Same problem. I manually created some of the registry values to attempt to get around the problem. It still persist. I say some, because the DLL has several COM classes in it. I created an EXE that creates the control differently and it works: Form.CreateObject("test", "oleobject","activexserver.class")
But my main project has it in a Classlib, with some additional code in it. No code in the INIT of the oleControl. The error that form gets is "Class is not registered". Which I see in the Registry it isn't, until I manually put those key parts it to get the other one working. Still get the same error in the main project.
Trying other things, but this one is challenging.
Thank you, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Eric Selje Sent: Thursday, March 22, 2018 5:01 PM To: profoxtech@leafe.com Subject: Re: ActiveX control refuses to register
I'm not sure, especially if the result says it registered successfully. Can you just put the control in the app's default folder so it can be found?
Eric
On Thu, Mar 22, 2018 at 9:53 AM, Tracy Pearson tracy@powerchurch.com wrote:
I have some client workstation that refuse to register an ActiveX control
I
use in my VFP app. Even manually typing the RegSvr32 command. The message that appears states it registered successfully. However, the Registry is never updated.
What ideas can I use to track down this problem?
Thank you, Tracy