I have one that has left me stumped for several days now.

The problem exists in both VB6 and VBA for Office. My more extensive instrument control and test are actually written in VBA under access (for the databasing and reports).

For years, I have used a very old ActiveX control LED.OCX.

My first Windows 11 machine was last December, an HP that was supposed to have Windows 11 on it but came from SAMS Club with Windows 10. HP Remoted and updated it to Windows 11 (HOME). All my programs, both VB6 and VBA with LED.OCX work fine on that machine.

Last week, I built up a new computer myself (gaming power machine), but it is still my shop's main desk computer. From the start, I installed Windows 11 Pro.

I can not get any of my VBA or VB6 Programs to see the LED.OCX control. I can reference it without error (it is not one you register with the OS) on both VB6 and VBA. The forms do not have access to it and it can not be found on the list of available activeX controls to choose from.

The main difference between the two Windows 11 machines is Home verse Pro. I do not use any of the pro features, so WIM should not be active. I do not touch bitlocker. So, I am not sure what the difference is. Both systems are 64 bit.

Thoughts, help, an LED.OCX alternative (would have to be backwards compatible to 32 bit Windows 7)?

Thanks kindly,

Dave