>>SQL Server and the current supporting technologies are set-based, while VFP is record-based. So you guys would need to develop some sort of translation going on for every DML command where SQL Server was the datastore. SKIP and GO "n" are not particularly set friendly.
>
>How about what I said? That woudl handle it.

As an example you can see what Powerbuilder does with the data window concept e.t.c. Powerbuilder uses native drivers to see several databases, but it can use ODBC as well. Maybe MS should build a native driver for SQL Server and have VFP plays the role Developer 2000 play for Oracle but even more of De

Of course everything now is build towards n-tier, but still you need easy ways to bind (in runtime or in development time ...) your client/or the middle tier component with the server: being the middle tier or the data tier ...
- The ability to have embeded SQL statements would be very usefull and easy to implement in VFP since it is an interpreter language ... For instanse i would like to write :
SELECT PRODUCT_CODE FROM PRODUCTS WHERE PRODUCT_CODE = "EEE" INTO :variable and the PRODUCTS table to be an SQL DATABASE table
or
SELECT PRODUCT_CODE FROM PRODUCTS WHERE PRODUCT_CODE LIKE "EEE%" INTO LOCAL/SERVER CURSOR dcursor, where dcursor could be binded directly (if it is a local cursor) with a grid or list e.t.c.
-I don't want to always go thru VFP views (or they could automatically created on the background ...) when i refer to tables from an SQL Database table or view e.t.c. For instance if i have an open connection in development time with an SQL Database i could use intelisense (because i have the info for the DataBase thru the open connection ) when i refer to any database object
-Easy way to make Data entry forms (one or one-to-many) beeing 2-tier or n-tier systems with data from an SQL Data Base (a lot of examples exist here from other rad tools like Powerbuilder )
-Extend the SQL syntax to be the latest ansi compliant (Still foxs sql syntax is limited in comparison with Oracle's for instanse ...)

These for now. I think is a very good idea to - additionally - market VFP as a client/middle tool for 2-tier/n-tier systems using SQL Server. This will be a very clear positioning

I propose the equation
VFP = (adoption of the positives of client server rad tools like Powerbuilder for easy client Server development) + ( tools to easily build n-tier/WebServices databased systems ) + (powerful local database engine for desktop applications or for manipulating easily the gathered data from any data source ...)

Thanks