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. Sure, there are issues like binding ADO Recordsets - and that is being fixed. However, I would also submit that the ADO is not that big a deal right now....ActiveBar works fine. The MS Agent works fine. VFP 6 fixed issues regarding the TreeView/ListView. Please Garrett, if you are going to make conclusions like this, back them up with facts - not conjecture....

Also, please tell me how VFP's lack of true Windows Control's affects your day to day development. Specfically, name for me 1 thing you cannot do becuase each control does not have an hWnd Property. Please don't tell me you can't use Visual Test. Yes, it would be easier - but there are workarounds. However, even that issue does not impede development. I have heard of issues with Citrix - but none of these appear to be really substantiated. I have used Citrix with both 2.x and VFP apps. Unless you use Citrix, this is not an issue. 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.......

>Because of all the ActiveX controls out there that only work in VB: I was hoping that this would make them operable in VFP. I know there are other issues, like VFP's lack of true windows controls.