Markus,

Thanks for your input.

>
>Part of this sounds kinda bogus to me. All COM objects have to support IUnknown and most of them support IDispatch (otherwise one has to use VTable binding). But the interface one creates in his own COM objects are neither IUnknown nor IDispatch. Our custom interfaces also support those two interfaces, but the actual interface we create with new methods (and what looks like properties) is a new interface all by itself.

I'm still trying to get my hands around the internal COM stuff. This helps clarify things a bit more. I would really like to see a whitepaper that describes COM from a VFP point of view and how VFP does things. Most of the VB stuff I've seen still assumes that the developer has done some C/C++ stuff. In otherwords, it expects you to already understand alot of the internals.

>
>VFP seems to do a fairly good job as far as the IDs go. It only recreates them when told to do so.

Right. It's an option on the Build dialog.

>
>With COM+, being able to implement different interfaces becomes a major issue. MS hasn't made any announcements yet, but I assume VB as well as VFP will be able to participate in COM+/ WinDNA environments.

It would not make sense for them to not participate.


>
>Markus