>This is an interesting debate....
>
>Playing nice and the ability to host UI elements such as ActiveX Designers are two different things. I think it has been fairly will documented that the emphasis is on VFP being a middle-tier solution.
>
>In your opinion, VFP will need the ability to support ActiveX Designers in order to survive. I don't entirely disagree. I think a better solution is to focus on what you can do today...

Yup....too many people worry about tomorrow. From my last few posts, it may seem like I'm one of them, but I'm not...I haven't figured out half of what I have now.

>using other tools that ship in the VS box. For example, if you want an Object-based report writer - use the one in VB and call it from a VFP component that requires its services. OO menus...I don't know how important that really is. Yes, an enhanced event model would be nice.
>
>I think the things to look at is Forms+, DHTML, etc. Like it or not...this is where MS is putting the resources, at least as far as UI development goes.

I totally agree with this.

>
>I just think it is time for folks to think outside of the VFP box.

I agree with this too. The absolute coolest tool to come around in a long time is the new Analyzer in VS. Anybody that has seen it should be jumping at the chance to learn all about it. I have it near the top of my list.

>
>In any case, I don't think one can conclude that VFP will support ActiveX designers. Yes, it would be nice. But, until I hear something from Redmond, I will take the conservative road and count on there being no support.