OLE error code 0x80040154 Class not registered

[FBCCA]

Our application is developed in VFP9 and we transitioned to a new server but afterwards, in one of the interfaces which has a date selector, the users are unable to view and access the date selector. The error shows as "OLE error code 0x80040154 Class not registered"
The files were copied fully from the old server to the new, how did this happen?
Accessing the page with the date selector on systems having VFP installed works, but not on users without.

 

[Chris Miller]

It's not sufficient for OLE classes (including OLE/ActiveX controls) to be copied over to a new computer, as the message says they have to be registered.

You better run a setup not just copy files over. That's generally good advice - do you not have a setup? If not, you better find out which OLE control has to be registered. As you say there's something used for selecting dates, it might simplpy be the good old MS date picker, usually an OCX file.

Chriss

 

[Mike Lewis]

An immediate solution would be to run REGSVR32.EXE on the target system:

From the coomand line:

regsvr32.exe <path and filename of the relevant OCX file>

A better long-term solution would be to create a proper setup system for your application. The aim is to create an executable, usually called SETUP.EXE, which the end-user can run, and which copies all the components of the app, and does any required registrations. You can do this with the cut-down version of InstallShield that comes with VFP, or use Inno Setup, which in my opinion is a superior product.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[FBCCA]

Hello.
We do not have a setup.exe
This concern is only regarding one computer that is why we would like to fix it on the one user system.
I was able to successfully run the regsvr32.exe using cmd for all the .ocx files in the target system win/sys32/ folder but the error is still present.

 

[Chris Miller]

It's not really helpful to run on all ocx files.

The major problem is you have to run elevted. So start the command prompt (cmd.exe) as admin, so Administrator is shown in the window title bar. like here:

Then change to C:\Windows\Syswow64 and use regsvr32.exe from there on the OCX file of your software, you might need to copy over another OCX that was not in the application directory of the older computer, but in some system directory.

Chriss

 

[FBCCA]

Found the issue was copying mscomct2.ocx to the user syswow64 folder and running regsvr32.exe for that file.
Thanks all