Be aware that the VB IDE hijacks the registry settings for your public classes when working on projects such as ActiveX DLLs and Controls. The IDE will temporarily replace (in the registry) the existing InProcServer32 for your class to a LocalServer32 entry pointing to the VB IDE version being run. Should VB crash in a nasty fashion, that registry entry will not be returned to its proper state. Then when you try to run your program “normally,” you will get various messages about the item not being able to run in multi-instance mode or other cryptic errors. You must simply restart the project inside the VB IDE and stop it again, putting things back the way they should be.