Hi Brian,

I run a test using your code which loaded table with over 3,000,000 records into CursorAdaper and I didn't get any errors moving through it in the Browse to the last record. Does it happens with only one specific table?

>
>Is there a limit on the size a cursor can be when retrieving records using the VFP OLEDB provider?
>
>Long story short, a client is converting all their VFP data to SQL Server and using VB components via the VFP 8 SP 1 OLEDB Provider to do it (heavy politics, don't ask). A problem arose where, for a table with 79 fields and only 111748 records, the provider is returning the following error after trying to move beyond record 12337:
>
>OLE IDispatch exception code 0 from Microsoft Cursor Engine: Data provider or other service returned an E_FAIL status
>
>
>I was able to duplicate their problem using the VFP provider with VFP code...
>
>First attempts were using a client side recordset, both connected and disconnected, and converting the recordset to a cursor via the CursorAdapter. Even with a connected client recordset, the cursor created only has 12337 records. When trying to loop through the recordset directly, MoveNext throws the above-mentioned error when trying to pass record 12337, even though EOF is false (which is what they saw on the VB side). Is there something that needs to be done to get the additional rows into the client-side recordset?
>
>Next I tried using a server side recordset. In this case a loop through the recordset directly hits all 111748 records, however, when converting to a cursor with the CursorAdapter, the resulting cursor only has 12438 records. So server side fixed their problem of getting to all the records with VB, but now I'm curious as to the size limit the VFP side when it comes to converting recordsets to cursors...
>
<snip>