I'm using CursorFill in the CursorAdapter and I tried the GO BOTTOM statement right after the call to CursorFill, but it didn't help.

>>I'm continuing to respond to you as I get more info, rather than responding to myself . . .
>>
>>This project has another programmer from another company on it and I spoke with him during a meeting today. He said he will see the same thing in Access. The ADO object is still being filled and is not available yet, however his next line of code executes and it references the ADO object and generates an error. He has used a technique of closing and opening the connection prior to proceeding or, alternatively, testing for existence of the object in a loop until it becomes available. I had already been thinking of the "loop" solution and created this procedure:
>>
>

>
>Not sure how your filling tcCursor, but in THAT CODE METHOD, add the line:
>Go Bottom
>Return
>
>

>
>that will force the data pull from the backend of choice. It has since FPD2.5 days in dealing with either SQL Server or vendor only db's and an ODBC connection.