fp file locking behavior

[Bob Haussmann]

Admittedly, this post is a bit of a fishing expedition, but 
we've exhausted our in-house testing abilities.  Platform is
Native Windows (ODBC) 5.6.01-5.6.06.

Occasionally (and unfortunately not in any way that we can consistently
replicate), we receive file locking errors in fpsql or rclerk on 
various index files.  These files are in active use, but only in
add/update mode (*clerk, not *report).  These don't appear to be 
record locks, but actual file locks.

The only clue we have at this point is that *clerk appears to open
the key and active index file for writing, even when simply browsing.
I would appreciate it if anyone else can confirm this behavior so
we can be sure it isn't specific to our setup (XP clients w/ Novell
client32 4.9* and Netware 6.5 server):

1) using any filepro database, take note of the "last modified" timestamp
of your key and index.A file.
2) start rclerk, select this database
3) choose "index selection" and a specific index
4) put any search criteria and start search
5) re-check the timestamp on the index file that was just used.

In theory, the timestamp in #1 and #5 should be the same, since this
was a read-only query.  In fact, if we take a copy of the file before this
process, and compare it byte for byte against the one modified in step 5,
there are no differences. 

Can anyone else verify this behavior on a different platform?

Thank you,
Bob Haussmann
Tabor Children's Services, Inc.