VB and Objects and Registries, OH MY!

Dear Dr. GUI:

I have looked everywhere to find the answer to this problem. Can you help?

In Visual Basic 4.0 (16- or 32-bit), I get the error message "Object server not registered correctly" every time I bring up the custom controls from the Tools menu. I know what the message means, but I don't know how to fix it. I don't know how to determine which "Object server not registered correctly," nor do I know what to do if I did.

I have tried re-installing Visual Basic 4.0 and updating my custom controls (about 840 of them), but I just can't seem to get rid of the error message.

First, how do I determine the offending object?

Second, how do I correct the problem once identified?

At Wit's End,

Dave Ryan

Dr. GUI replies:

You are certainly a determined person to re-install and update about 840 custom controls. Come sit on my couch and we'll talk about your childhood....

After putting in all of that effort, you may hate me for what I am about to say—but there is an easier way!

It is a little program called REGCLN.EXE that comes with Visual Basic 4.0. Its purpose in life is to do just what you are looking for—remove corrupted and unwanted "stuff" from the registry. You'll want to get the updated version (version 3.0) from either of two Microsoft sites: the Visual Basic part of the Knowledge Base (http://www.microsoft.com/kb/ search for q147769.htm), or the SoftLib/MSLfiles folders at ftp.microsoft.com.

What REGCLN does is to remove any corrupted entries from the registry, "cleaning" it up. Think of this program as a "ScanDisk" or "ChkDsk" for your registry. Once you've used REGCLN, install the missing control(s) and you should be back in good health.