PxPlus User Forum
Main Board => Discussions => Programming => Topic started by: joe on May 27, 2020, 04:15:43 PM
-
I have an old XP machine where I can enter DEF OBJECT X, "[WDX]*" and get a long list of objects I can connect to.
On a windows 7 machine the list is far shorter and I don't see the one I need. I have tried to re-register the OCX to no avail.
Any tips on register an OCX for use with WINDX.
-
A little more info on this subject. It appears it may be windx issue. The machine that fails is running version 9.10
hopefully that will jog a memory from some of the old timers. ;)
-
I am not sure when the introduction of powershell was introduced to windows, but I have also found the same command def object x,"*" to be very limiting regardless if on the server or via a windx client.
If the Windows 7 client has powershell, you can always use the following command to retrieve a list of ActiveX objects you can instantiate although many are O/S specific.
gci HKLM:\Software\Classes -ea 0| ? {$_.PSChildName -match '^\w+\.\w+$' -and
(gp "$($_.PSPath)\CLSID" -ea 0)} | ft PSChildName
Hope this helps!
-
This functionality still works on Windows 10.
Perhaps the OCX you are looking for is not installed or available on the PC that is running WindX.
What specific OCX are you looking for?
-
Thanks Josh,
I saved your answer for a rainy day. Hope you are doing well.