George,

I suspect that you are correct, and I also recollect a post that, in particular, VFP has problems with anything (ActiveX) involving a 'container'.

BUT. . . We have been told that VFP continued this for the puprose of maintaining a MAC capability. As we all know, VFP *NO LONGER* is supporting MAC, as of Version 5.

This being the case, one can legitimately conclude (another word for 'guesswork') that actual Windows Objects would have been included in VFP 6 and, since this was not the case, that is one of the prices to be paid for focussing VFP on "middle tier". They are simply not needed for mid-tier work.

Is that good for us (developers of business apps in non-enterprise situations)???

Regards,

Jim N

>Hi Bob,
>
>I'll only touch briefly on the ActiveX containership question. Be forewarned, however, that this is pure guesswork on my part, although it does have some basis from MS documentation. I read something recently on exactly why the Coolbar control doesn't work. If I recall correctly, one the reasons that is a problem is that VFP objects aren't Windows standard object. All Windows standard objects have the capacity to process messages. I don't that VFP's have the ability. Therefore, unless there are some very fundamental changes in this area, I think that it's highly unlikely that you'll see improvement in this area. However, if someone on the Foxteam, or someone more knowledgable about this says otherwise, I'll happily retract this.