Similar functionality can be found in TweakUI for XP. But this rocks and is a lot easier than having to set up those associations. Good find!

Incredible. Thanks for the quick and informative reply, kilowatt. The odd thing is that the #import IS indeed in my idl file and I still get "unresolved type declaration". The second method (which I didn't think of) should work, but I would really like the first method to work if possible. Also, is this the "right" way to write a data abstraction layer? I would rather not have different rdbms code comingled in the same dll and unfortunately for this project, stored procedures aren't available. EDIT: The #import is pointing to the BaseData.dll, if that helps. Thanks in advance.

Before I get started, I should warn you that most development I have done has been in VB. Now that the laughter has subsided, here is the problem: I have the following: IBaseData - An interface in a dll which will not contain any implementation code. ISybaseData - An interface which I would like to inherit from IBaseData INSTEAD of IDispatch. I get an error that says unresolved type declaration IBaseData in the SybaseData project. Does anyone know what I am doing wrong? EDIT: The SybaseData dll has a static link (#import) to BaseData project. Is that wrong? Note: When I have BOTH interfaces in the same project, and I hack around the .idl file it works fine and I get the desired effect. But when I try to inherit it from another project (dll) I get that error. Goal: To be able to do have a client app have a static link to the BaseData dll. After I create the smart pointer, I can then load by Classname "SybaseData.MyData" onto the smart pointer because they export the same functions, but a different implementation. In the future, I would like to create a "OracleData.MyData" dll and so forth and so on. Am I going about this the wrong way? I would rather not do use Invoke because it is a pain to set up. Please let me know if you need any clarification, as the entire post is probably a bit confusing ;)