Bonnie,

>PMFJI, but your description of ADO.NET ...

>>It is a wrapper on top of OLE DB or ODBC.

Among beeing a OO datastorage with some vary basic DML, it is also a wrapper on top of OLE or ODBC.

The point I was trying to make is in the light of an earlier discussion John and I had about this subject: If ADO.NET supports SQL. In this respect ADO.NET is just a wrapper. ADO.NET on the API retrieval side does not have any intelligence of the concepts of SQL. It just passes the SQL through OLE DB or ODBC.

That beeing said. If you don't use a backend to rely on, ADO.NET cannot be regarded as a Local database engine because it misses a lot of what a database engine should be capable off. The is no way you can do any SQL on local datasets this way.

>... is not accurate or complete. Sure, there are classes that get your data from SQL Server (or VFP or whatever else) through OLE DB, but the ADO.NET DataSet, through which all of your data manipulation is done, is a disconnected DataSet having nothing to do with OLE DB. I guess I missed your point ...

Walter,