I've just run into a serious problem with VFP9SP1 OLEDB where a simple query with only aggregate functions such as SUM(*), when run against a table with no matches to the WHERE criteria, returns an incorrect result. Instead of returning a recordset with RecordCount equal to 0, it erroneously returns a recordset with RecordCount equal to 1, and the fields in that record hold null values rather than valid numeric valuse. As you might imagine, this is a serious error that causes the app to crash everywhere such a roll-up query is executed with no matching input records.

I switched back to the VFP8 OLEDB driver dated 25/8/2003 and the problem went away.

>Hi folks. In the last few weeks we've converted our ASP.NET 2.0 application to use VFP9SP1 OLEDB provider instead of COM components. Though very fast, we are getting some errors that appear to be false.
>
>Errors such as:
>- cannot find table zero
>- database is invalid, please validate
>- index is corrupt
>
>When I open the tables or database with VFP9SP1 and validate them they are fine. I've tried to pin this down in our test environment and on our server, but the errors happend sporadically on the exact same code.
>
>Finally, my questions:
>- Is this version of the OLEDB provider flakey?
>- Has anyone else deployed ASP.NET 2.0 and the latest VFP OLEDB provider? What is your experience?
>- Is the VFP8 OLEDB more stable?