Hey buddie,

>As far as I know, you have to use two separated DLLs, as an interface is based on the vtable of the target DLL. I mean you need to access the other one's Type Library.

yeah, but it's a bummer that VFP doesn't have an option to check for interfaces defined in the same project. I mean, when we build the project, it goes througout all the classes and build the TLB from there. That said, it should have a way to say "IMPLEMENTS interfaceX in this project". :-/


>Why do you need to put both on the same DLL? It is just a matter of saving the quantity of DLLs?

For one thing, yes, saving the quantity of DLLs is always a good thing when we are trying to avoid DLL-Hell. For other thing, this classes and interfaces that I have are really related and it doesn't make sense to having them in two separate projects. But I think I'll have to end up creating one project for the class and one for the interfaces. Argh. I thínk .NET has already spoiled me as far as working with interfaces goes. :)


>See you (in a couple weeks? Seattle?),

Hell yeah! :)