Kelly,

In the interests of balance, perhaps you might ask JVP to justify his previous assertions that VFP's remote data access is like a "pig" or a "whore" (sic), or that VFP is only used for po-dunk development. Or the apparent attitude that whenever one discusses VFP's "doing" data it only includes local tables, so that any anecdote where SQL Server is better than local tables means VFP is no good.

In this case: I've "done" data using both VFP and dotNET using C#. IMHO: by comparison, dotNET has been absolutely horrible. Of course I started even before release 1.1 and was comparing it to full use of VFP's productivity features... e.g. rather than writing screeds of code to prevent SQL injection or wasting time writing massive Stored Procedures to handle partial parameter returns, I used native VFP features that took care of it for me. Developers who do everything by hand or avoid persistent local cursors or use hardcoded ADO may not appreciate the difference.

Re latest dotNET data changes: well worth review by VFP people. In view of the propensity of others to boast that they predicted this and that, I am delighted to point out that I predicted much of it in 1992 and was scoffed at by- guess who? - who denied such facilities could ever be desirable in dotNET!

Regards

j.R