The manual says when you enable strict change detection:

"What this means is that every operation that requires reading of data from a table such as moving between records, filtering, setting ranges, searching, etc. will cause DBISAM to check for changes before the operation is executed. If DBISAM finds that the data in the table has changed.."

What exactly does "data in the table has changed."  mean from the client's point of view ? Does it mean any change at all, made by this session or any other ? Or does it mean a change made only by another session ? As in, changes made by this session don't count as change, because it knows about them in its local cache copy.

I'm hoping it's the latter, that only changes made by other sessions count.

Arthur,

<< I'm hoping it's the latter, that only changes made by other sessions
count.  >>

Yep, that is the case.

Tim Young
Elevate Software
www.elevatesoft.com