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?


Hi Sergey, thanks for replying. Yes, so far it is only happening with one table, and it is the main one for a legacy app. How many fields did your test table have?

As a test I deleted a bunch of fields from the table, basically every one except the four that make up the natural key. After doing that all the records were available in a client-side recordset and in the cursor created by the CA. So I'm not sure if it's some kind of size limit (# of rows and # of fields) or perhaps there is a bad chunk of data somewhere.


- Brian