LED.OCX / Windows 11

David Kuhn 1 Reputation point
2022-09-13T16:31:14.167+00:00

I have a new machines with a new copy of Windows 11. I can not register (regsv32.exe LED.OCX) is either the syswow64 or the system32 folder.

I have an older Windows 11 machine that 9 months ago, I was able to register LED.OCX on. The machine, an HP, started life as a Windows 10 computer. It was supposed to have Windows 11 on it, so HP support remoted in an updated it to Windows 11. Afterwards I set the machine up as needed and it was able to register LED.OCX.

Maybe that is the difference. I have never had a problem using the OCX control before. I use it primarily on VBA forms and code on top of Access. I also use it on VB6 programs, but not as much.

This LED.OCX is a control that you can add to an Access Form that looks like a LED on an instrument's control panel. You can make it any color and cause it to blink. If there is another LED type control, I would lover to know it.

In the meantime, I try to register in under windows 11 and get the error "The module c:\windows\syswow64\led.ocx failed to load. ...bla bla bla... The specified module could not be found". I can do a DIR LED.OCX and it is by all means there.

Thoughts/help/alternatives please.

Thanks all very kindly,

Dave

Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,290 questions

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. David Kuhn 1 Reputation point
    2022-09-13T19:08:25.5+00:00

    No, just the standard "Make sure the files exists.... No error code"

    I'm wondering if it ever registered now and if I am not having an access issue? The LED.OCX is referenced in access, but the LED control is blank and not available to pick from in the list of activeX controls. Under references, is shows it just fine. In the trust center for access, I have it set wide open.

    I can not figure out the difference between the two Windows 11 machines. My Windows 10 machines runs it just fine, my couple Windows 7 machines run it just fine too.

    I was assuming I had to register it, but I did find other controls that were not registered just referenced in the VBA Code IDE.

    Do, not sure if it's a windows 11 problem or an office problem. I am running the exact same 32 bit version of Office 2016 on all machines (I like the development environment better than 2019).

    Stumped

  2. David Kuhn 1 Reputation point
    2022-09-13T19:51:25.233+00:00

    I just check on a Windows 7 computer, which ran it with LED.OCX it is not a registered activeX control. It just has to be referenced in the the code IDE behind the Access form, to which it is, and has no problems adding it. The form itself cannot see the control. With the exact same version of Office 16 on the other Windows 11 machine, it is fine.

    I'm have tempted to uninstall office reboot and reinstall it. I dunno. This is the first time I have had issue with the activex control.

  3. David Kuhn 1 Reputation point
    2022-09-13T20:02:32.743+00:00

    I just tried in a VB6 project and it can access the LED control. It is used a lot in that particular program. On the other Windows 11 machine, just fine. <sigh>. I give up for now.

    0 comments
  4. David Kuhn 1 Reputation point
    2022-09-24T22:26:31.177+00:00

    On a second Windows 11 Pro machine, the LED.OCX will not work in either VBA or VB6. In the Windows 11 Home machine, it is working fine in both environments. grrrrrr

    I wonder if I can downgrade from Windows 11 Pro to Home?