Hi!

>>Well, you can make just a now control. For example, I wish Grid reconstruction behavior is fixes finally (see FAQ#8019). If you think it will impact existing applications - well, you can jsut create ... new grid control. And this will not have ANY impact on the applications we ship. Using such approach there could be solved a lot of things.
>>
>
>Careful there. Do you really want a VFP default toolbar with 2 grids, 3 buttons, 3 listboxes, 4 textboxes, all with different names, but with different enhancements to the same basic functionality? All in the name of backward compatibility? I don't.
>

Its better than nothin, again, in the name of the backward compartibility. MS do not implement certain features and fixes because compartibility...

Anyway, the View Classes button in toolbar can have additional menu item - select Standard or New classes.

>>As about the coding, there are certain commands that are quite hard to implement and require a lot of attention from programmer. For example, late binding of VFP code to ActiveX object events. Use of VFPCOM.DLL takes some time from VFP developer. Why this could not be included into the VFP, but just use somethign external?
>
>Check out the EventHandler function in VFP 7. It is internal now.

Good to know that.