Hi Walter,

>If a table is not opened exclusively it could be that this won't affect performance. A NT server can use Exclusive oplocks to provide a sort of exclusive mode even when you opened the table with the SHARED clause or having SET EXCLISUVE OFF.

I can't speak for Windows NT, but I tested this a long time ago on FoxPro DOS. The same operations took 300% more time on a table that was opened in shared mode, compared to exclusive access, and the table was not accessed by any other station. We finally traced it down to the number and size of packets that FoxPro sent. With shared mode it transferred more and smaller packets than in exlcusive mode.

>Like you noted, Even if this tables is used by another user It only seems to reread the index when any modification was made to the table. I'm curious how this internally works.

Probably a time stamp, or something like this. If it's not identical, VFP reads the index again. But I only guess here based on my and others observations.


Christof