Were all client workstation applications installed the same way? Was the reference in the client application to the OCX to the \%SystemRoot%\system folder or \system32 in the uncompiled version. Look in the class and see where the client application is referencing the OCX. Sometimes, if the pathing is different between installed and uncompiled version, it may not find the OCX. Also, does the OCX require an accompanying .dep, .gid, or .lic file? Lastly, look in the registry at the registration and see if there is a naming problem between the uncompiled reference and the ocx. For example, an .OCX called CTSCHEDULE.OCX, may be referenced in the class as CTSCHE~1.OCX but by the long name in the registry or vice-versa. This shouldn't cause it not to work, but I have seen strange things like this, when conformed, all of a sudden cause the situation to clear up.

HTH,

>Hi all,
>
>I've built a new control using VB and I installed it and registered it on all the computers that will need it. Every registration succeeded on all the computers.
>
>Then, when I run the application on the computers everything runs fine on all but two computers. On those two computers, I get the following error message when the user tries to open a form that uses my control:
>
>"OLE error code 0x80040154: Class not registered. OLE object is being ignored. Record number 16."
>
>I don't get it! The registration was succesful on those two computers and everything else is working fine. What do I need to look into?
>
>Thanks in advance, Stephane.