none
Register OCX in 64 bit Windows 7

    Question

  • I have been working on an Access Project for a while using  Leban's RTF2.ocx on Windows XP 32 bit. My PC was updated to Windows 7 64 bit and I cannot register this OCX file. I get the following error message: "The module "RTF2.ocx" failed to load. Make sure the binary is stored at the specific path or debug it to check for problems with the binary or dependant .DLL files. The specified module could not be found."

    Is it possible register this 32 bit OCX in 64 bit Windows 7?

    Tuesday, June 07, 2011 3:38 PM

Answers

  • Found the original executable for this OCX install. Had to run it with compatibility mode and as administrator.
    • Marked as answer by Rick131 Friday, June 10, 2011 11:59 PM
    Friday, June 10, 2011 11:59 PM

All replies

  • Have you tried to use 32-bit "Regsvr32" with the DOS command?

    I'm not sure if it would work in 64-bit windows as most of us avoid using ActiveX.
    Wednesday, June 08, 2011 1:03 AM
  • Yes. I tried putting it in the c:\windows\system32 and c:\windows\sysWOW64 folders and get same result.
    Wednesday, June 08, 2011 1:27 AM
  • Run Depends and see if all of the module's dependencies are available.  The link you supplied mentions two dependencies - the 2 VC runtime files, Mfc42.Dll and Msvcrt.Dll and it requires a minimum of Version 3 of the Rich Edit DLL. It is possible that they have dependencies that are not in Windows 7 -- x64 or x32.  The last update to this product was seven years ago.  Things have changed a bit since then.

    By the way, you can register a 32 bit OCX in x64 Windows 7 if all of its dependencies are available.

     

    Wednesday, June 08, 2011 2:36 AM
  • I don't know what Leban's activex dependencies are or what is required. Leban is no longer involved in Access, kind of hard getting answers here.

    Here's link that might help but it's different. Look at Ming Yang suggestion to see if it helps.

    http://social.msdn.microsoft.com/Forums/en/sbappdev/thread/91cf3127-70fe-4726-8a27-31b8964430c5

    Wednesday, June 08, 2011 7:40 AM
  • Found the original executable for this OCX install. Had to run it with compatibility mode and as administrator.
    • Marked as answer by Rick131 Friday, June 10, 2011 11:59 PM
    Friday, June 10, 2011 11:59 PM