Hi George,

>Try http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/sql/deploy/depopt/SQLFOXPR.asp

This article is rather old, and handles some problems with RVs. According to the article one of the problem with RVs is that error handling is more difficult.

I tend to disagree here, because the article does not mention anything about the possibility to capture ODBC errors via the AERROR function. Maybe this article was based on VFP 3 or 5 and the AERROR function did not handle these errors. So I think the conclusion today would be slightly different.

Between the lines I read that RVs are a powerfull mechanism when it comes to portability, because the ODBC driver provides more transparancy. The manual work that comes with SPT makes it harder to incorporate this into frameworks.

Of course SPT provides more flexibility, but then again, flexibility is not a goal on itself. C/C++ provides more flexibility when writing database application, but we as VFP developers are more interested in the RAD characteristcs of a database tool.

As always two techniques are seldom mutual exclusive, they can be used together. Therefore I tend to use RVs for simple input forms and reports, but for the stuff where more power is required I have (to my regret) revert to SPT.

Walter,