Hi Larry,

I probably should refrain from posting general experience comments late at night when too tired to read the entire KB. <g> I was providing some general experience with my past issues with DBI controls, doing some control building with MFC and with other apps getting broken by newer MFC versions and by security updates. It's true that if they had subclassed the controls and were doing some of their own WM_CHAR handling that this could have broken the control. I have also been in Kirk's position of getting feedback from DBI as to it's not our problem it's a VFP issue. And yes there are some issues that are VFP issues but then some are not. So, I was mostly referring to my past experience with DBI. Hopefully it can be worked around or resolved.


> Rich,
> I'm confused. MS fixes a bug and you say this causes a problem? It sounds to me that the developers of the
> control programmed to the bug and now they are paying the price.

> In my mind it's similar developers to writing "bad" SQL statements in VFP versions prior to 8 that didn't
> include all non-aggregates in the GROUP BY clause. When MS "corrected the issue" in VFP 8, many developers were left hanging.