>Tamar,
>
>Use gofish4 to check every USE in the processing section- USEing a table or view when the culprit view's underlying dbf is selected can cause an unexpected error that doesn't show up until the requery(). It may be that the record where it breaks does something slightly different and causes this.

As I said in another message, I ran a full set of LIST STATUS (that is, for each data session) into my log just before the requery that fails. Search the log result shows each of the tables used by the view open only once and they're in the right data session.

>
>On principle I'd make sure virus scanning is off (including on the server) and reindex the table.

Pretty sure the client reindexed and checked for corruption before they brought me in. (In case it wasn't clear, my client is the company that makes and sells this vertical.) I'll check with them about virus scanning.

Tamar