Jump to content
Rolling Thunder Forums

RichTxt32.ocx file missing


Recommended Posts

Do you actually have the file somewhere on your computer? Perhaps under c:\windows\system\tdbg6.ocx ?


I assume the files I emailed you didn't help?


FWIW, this site has a copy of tdbg6.ocx (and a few others) for download and instructions to run "regsvr32.exe c:\windows\system\tdbg6.ocx" on it to register it, which it sounds like you've already done?:




It is microsoft windows, so I'm sure you've rebooted a few dozen times? Bill likes it when people reboot.


I don't suppose you have a copy of Visual Studio you feel like installing.


At least you are not totally out in the cold like the Mac and Linux users.

Link to comment
Share on other sites

Here;s what Microsoft says about it. Sounds like I have incompatible OCX files. So could I solve this by downloading compatible OCX'es?


Run Time Error 438 - Object Doesn't Support this Property or Method

The most common cause of error 438 is not maintaining binary compatibility between successive versions of your components. Each COM interface has an associated GUID that is called an interface ID (IID). Each coclass has an associated GUID that is called class ID (CLSID). When you compile an ActiveX component in Visual Basic, the CLSIDs and IIDs are compiled into the component's type library.


A program that consists of a Visual Basic client and an ActiveX DLL is released to the user community. At a later time, additional functionality is to be added to the DLL component. The necessary modifications are made, and the ActiveX DLL is compiled without maintaining binary compatibility. When the DLL is released, the client that is trying to use the DLL will throw run time error 438. The reason this occurs is that when the DLL was compiled, a fresh set of GUIDs was compiled into the DLL, and the client has no reference to these new GUIDs. This is why it is important to maintain binary compatibility with the last-released version of the component when you are trying to release a newer version.


Another example for the runtime error 438 would be including the wrong version of Microsoft Data Access Components (MDAC) in the distribution package. For example, a Visual Basic 6 Service Pack 5 program is built on Microsoft Windows 2000 Service Pack 2 by using the latest version of MDAC that is present (version 2.6). When the distribution is built, an earlier version of MDAC (version 2.5) is used (unless MDAC 2.6 is downloaded), causing an error 438 to be thrown when the distributed program is run.


Another scenario would be misspelled method or property names, and this scenario is described in the following Microsoft Knowledge Base article:

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...