One final post on this technical discussion. As usual, in any situation there are those who refuse, absolutely refuse to accept reality, the truth so to speak.

First, and I've said this several times before, I find it laughable that people make the statement as Walter has done here that VFP does data so much better then other tools. Almost saying that it's impossible to create a real app with anything other then VFP. We all know how wrong that statement is.

I think the only thing that VFP did was make the barrier to entry into programming low. The end result of this is I've personally seen several instances of non-programmers (typically accountants, but others as well) getting hired by non-it depts of companies to put together apps. It got called in because of issues (corrupt DBFs or other issues).

Rightly or Wrongly, this type of app helped to get VFP on the not-accepted list at these companies. Security issues was another hugh concern.

>Walter, it absolutely astounds me how you miss the facts and misrepresent positions. My comments in-line....as you're now treading on the area of making false public statements, I hope you read this carefully.
>
>And also the fact he bought his MVP title with an MSDN article how to do ADO in VFP, ADO ??????
>
>John was an MVP at the time he authored the MSDN white paper. He wrote for FoxTalk, spoke at user groups, wrote books, and spoke at conferences. Again, since your knowledge of the timeline is so far off, you're better off just worrying about your own business than his.
>
>By the way, that paper was commissioned by MS - it was a very popular white paper.
>
>
>John's knowledge was skewed and extremely biased which caused all the fuss up here. Seriously how could anyone with a straight face say that .NET1.0 was just as good with data and RAD as VFP?
>
>Well, that depends on how you work with data. If you do so in a generic manner, then the specific toolset does not matter. The fact is, JVP stopped using Fox DBF's over 10 years ago, in favor of SQL Server and stored procs. I stopped using the DBF five years ago in favor of the same thing. With data logic in SQL Server, VFP just isn't' as important as it once was.