>>>>It does make for an interesting topic - "What if VB got inheritance?????"
>>>
>>>If VB got inheritance, You just might see me jump ship for a bunch of projects. I would only use VFP for projects that wanted native data (that's still a lot).
>>
>>I think I would too.
>
>Hey Guys, let's be positive. can't we discuss the "What if VFP had more VB elements?" I'd stick to VFP then ;-)
>
>KR,

If VFP learned to host ActiveX controls better (and bind them to data), if VFP gained support for early binding COM objects, if VFP gave the option of using real window handles for its controls (not going to happen), if VFP made it easier to use pointers and structures for Win32 functions, if MS decided to push VFP as hard as VB, then I would stick with VFP no matter what. (I probably will anyway).