<much snippage follows>
>This is simply not true. Yes, there are controls that do not work well with
>VFP. However, I would submit that most controls - work fine. Simply put, you
>can't substantiate what you are saying and concluding here.

"Most controls"? That goes against everything I've been hearing... Heck, MS can't even get the Web Browser control to instantiate correctly.

>Sure, there are issues like binding ADO Recordsets - and that is being fixed.

For which I applaud the team: I can hardly wait to be able to pass recordsets out of DLLs. It will make component design a lot easier.

>However, I would also submit that the ADO is not that big a deal right
>now....

Arguable, but not in my day-to-day....

>Specfically, name for me 1 thing you cannot do becuase each control does not
>have an hWnd Property.

Put something on top of an ActiveX control.

>So, barring these issues I have brought up - please tell me how the lack of
>true Windows Control's negatively impacts your day to day development.......

Day to day? Not much. However, I'm still waiting with interest for someone to explain to me how Active Accessibility works with VFP, rather than just saying 'Yes, it works...' I can't test it myself, because I don't have the equipment I'd need (you want me to try to justify a screen reader to the budget people here? :-) ).