Ed,

>Ed, you can write OO record-oriented code; you can write procedural set-oriented code. The native OO tools in VFP work well with view-oriented, set-oriented processing, and portability of the data services layer of the application to a backend environment is significantly easier if you already think in terms of SQL DML operations. Rather than add yet another xBASE layer that does nothing more than emulate set-oriented behaviors

I think you're wrong here. This has nothing to do with emulating. Its by itself a set oriented behaviour and if you ask me a far better one than the implementation of SQL-views.

>, I'd rather see the VFP team strengthen the native SQL support to do things like nested subqueries,

Talk about performance-killers.

>and give VFP the ability to deal with ADO recordsets in the same fashion as it deals with native cursors, making it a better player in the distributed computing, COM/COM+ environment.

Here we agree.

Walter,