OLE Error Code 0X80040154

[ChrisRChamberlain]

I have application that when installed from a distribution disc searches for an OCX file. On cancelling from the dialog, the error message is :-

OLE Error Code 0X80040154. Class not registered. OLE Object is being ignored. Record No nn.

After the third attempt, the application loads and runs as normal.

The application's class library requires ..\vfp\ffc\_base.vcx, ..\vfp\ffc\_format.vcx and ..\vfp\ffc\_hyperlink.vcx

As there are 3 errors, logically relating to these 3 libraries, what's the easiest way out, apart from creating a new class library?

TIA

Chris

 

[foxdev]

I'm not clear if this is your application or when you've received.

In either case, it appears that the setup disks creator did not check the options for installing the ActiveX controls in Step 2 of the Setup Wizard.

 

[ChrisRChamberlain]

foxdev

Thanks for your response.

I had unknowingly included a development form in the final project with 2 .ocx's which were not registered as you suspected. Confident all .ocx's are now registered.

The file dialog no longer appears but there are two error messages as before, record nos 21 and 22.

Version is VFP 6.0 SP3.

Chris

 

[foxdev]

Chris, are you still getting the "class not registered" error?

If so, one possibility is that these controls are not licensed for distribution. This is especially likely if these are third-party (non MS) controls, which may have a "design-time" license, but not a "run-time" license. The OCX controls are smart enough to know when they are being installed in a run-time environment, and may refuse to be registered (or run) if the author's license precludes it.

Just a hunch, but I've seen it frequently.

 

[ChrisRChamberlain]

Robert

Yes, "class not registered".

The 2 remaining and offending .OCX's are now determined to be Microsoft MAPI Message control, version 6 and Microsoft MAPI Session control, version 6, O/S being WIN 98.

They were checked in the second stage of setup but disappear from the file list, hence the installation failure.

I assume these are licenced for distribution?

As a workaround, this feature has been removed from the project, and setup is normal.

I also reinstalled SP3 for good measure.

Chris

 

[foxdev]

Hmmm :-( it should be OK, because according to the VFP docs:

ActiveX controls (.ocx files) are installed by default when you install Visual FoxPro. You can distribute ActiveX controls with your applications.

Sorry...out of ideas.

 

[ChrisRChamberlain]

Robert

I should have looked harder at the NetSetup report.

The .ocx's were there. Problem actually with User machine - it had had a newer version of WIN98 installed over the original, not always a good idea.

New WIN98, no FoxPro problem.

Thanks for your help.

Chris [sig][/sig]

 

[dhayax]

halo.. chris !,
i give you two way out :
1. You change your computer
2. You create another program

bye....

[sig][/sig]

 

[shangrilla]

Hi Chris:

I just ran into the same problem. It is a user specific Win98 porblem. The app runs fine on one win98 box, but it gives error ox80040154 on another one. Do you happen to know what was wrong with the win98 box you were dealing with and what you did to fix it?

Thanks

 

[IRABYY]

FYI: I have had similar problem with RichText OCX and Common Controls OCX, both are being MS controls, on Win98SE machines. Uninstalled and installed several times - same thing: OLE errors.

Turned out the machine had outdated ComCtl32.OCX/DLL files (size of OCX was something around 150K). I checked it on my and other machines (other 98SE, ME, NT4 and NT5) - the size was between 500K and 600K. So, if you include them into your setup kit and make them "Always Install" in InstallShield project it should work. If you are using VFP6's own Setup Wizard (s./b. named "Dullard"!) then you'd probably be better off providing the procedure for replacing the old OCX/DLL with the newer ones on end users' machines (which I did).

Hope this would be of a help for you.

Regards,

Ilya

 

[ChrisRChamberlain]

shangrilla

I really don't remember the details but I believe it was simple a case of formatting the drive and starting afresh with Win98 SE.

IRABYY's experience may be more helpful to you.

FAQ184-2483 - the answer to getting answered.​

Chris