>Now... this seems to stick in the craw of many. Why, has the FoxTeam not changed the UI ogbjects so that they are true windows objects. This issue has been blamed on several things that seem to be holding VFP back in the eyes of many... stuff like...
>
>1. Slow Screens
>2. Bad Active-X support
>3. No test tools work with it
>4. Poor performance with NTS... (NTS is the best easiest way to create a thin client product... but, due to VFP's screen handleing, the performance is not up to par with a VB, VJ++, or VC++ front end?
>5. Add your gripe due to this 'anomoly' here!
>
>Would it be simple for the UI objects to be replaced? My feeling is NO.
>
>Is it doable? My feeling is yes.
>
>Will it have a major positive impact? My feeling is MOST DEFINATLY!
>
>BOb
>
>I think the above is also why the VFP toolbar does not support functionality and the looks of Office toolbars or IE toolbars. I think the above would allow them to ship the toolbar classes that all of there other tools and aps use.

Hi BOb,

I think it's more than just the objects themselves. I think that Rick Strahl pointed out that the entire VFP handling of Windows messaging doesn't conform to the "standard". My experience in this area (as well as his reputation) leads me to believe that he's absolutely right. If so, it'd be a major undertaking to bring it in line. I believe that I've also heard we'd lose a great deal of the ease with which the objects are related to the underlying data. This would cause major problems in making conversions to the new version. So the real question is, would we gain more than we'd lose?

My experience is that 6.0 is much better with ActiveX than 5.0 was, and I'm sure we'll see some more improvements in 7.0. However, some controls may still present a problem.

The MS Toolbar works fine to create the MS/IE toolbars. Certainly there's a bit more work involved, but it does work.

As a side note, we do have "real Windows objects" in 6.0. These are the controls with the names beginning "Microsoft Forms 2.0..." I don't know if these may work with some ActiveX containers simply because I haven't tried them. My guess, however, is that they won't because of the differences in messagaing. But that's a guess.