>>The real issue is that VFP needs to better support that ActiveX instead of adding a new StatusBar baseclass to the language.
>
>I think the real issue is that ActiveX is "dead" (IMO) and that VFP is behind the curve (again) as an MS product. DLL Hell.
>
>.NET has in effect abandoned ActiveX and only supports it via wrappers; TreeView, ListView, Scrollbar, Grid, Calendars, Common Dialogs, STATUSBAR, etc. etc. are now all native (classes) in .NET.
>
>VFP should get with the program (MS has the know-how in .NET).
>
>(One of these days I'll talk myself into switching to .NET permanently).

It's kind of interesting though how screwy the .Net common controls are implemented. They obviously used the Win32 API model not the ActiveX model and many things take a lot of code to do right. THey're also not very fast, which was a big surprise to me. Lots of flickering etc. even with moderate amounts of data...

Some things change, but don't necessarily get better, huh?