Brian,

I lean toward some kind of corruption in the table. To verify that, you can create a table with the same structure, fill it with random data and see if it blows up AD access. If it does, than it's a bug, otherwise it's data corruption.

>
>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.
>
>