PxPlus User Forum

Main Board => Discussions => Programming => Topic started by: joe on July 16, 2024, 06:19:29 PM

Title: def object x,"[wdx]*"
Post by: joe on July 16, 2024, 06:19:29 PM
when I issue that command from various (64-bit) versions of providex I get different results in the window. Primarily on one version I get sigsign.sigsignctrl.1 and the other sigplus.sigplusctrl.1.
What controls which one I get. I need it to always be sigplus.sigplusctrl.1
Title: Re: def object x,"[wdx]*"
Post by: EVa on July 17, 2024, 05:03:49 AM
AFAIK, that listbox shows registered ActiveX controls that have a 'Control' subkey.  In other words, when you start REGEDIT and go to HKEY_CLASSES_ROOT\WOW6432Node\CLSID, all keys in there that have a 'Control' subkey, like for example:

HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{CA8A9780-280D-11CF-A24D-444553540000}\Control

(Adobe PDF Reader).  So if one PC shows sigsign.sigsignctrl.1 and another one shows sigplus.sigplusctrl.1, I would expect the registry entries to be different.
Title: Re: def object x,"[wdx]*"
Post by: joe on July 17, 2024, 11:14:28 AM
This is the same work station.
Title: Re: def object x,"[wdx]*"
Post by: Mike King on July 17, 2024, 03:51:29 PM
Sigsign/Sigplus are from Topaz systems.  You may need to contact them as to why the difference.

According to https://topazsystems.com/software/sigsign.pdf sigsign uses sigplus.
Title: Re: def object x,"[wdx]*"
Post by: Mike King on July 18, 2024, 12:33:20 PM
One thought -- you said you are using different versions of ProvideX (this should be PxPlus otherwise you need to contact Sage).  Given this please doublecheck that all versions are  the same -- either 64 bit or 32 bit. 

The display of installed ActiveX controls will vary between 32 and 64 bit installations as each will depend on the software installed and whether it was 32 or 64 bit.