We found the setting that caused that behavior. In Novell client, the default for File Caching is On. I think this is the default setting.

After setting File Caching = Off, everything worked fine. Same for both computers.

They are using the latest Novell Client for XP.


>This is definetively caused by some configuraton error on your system! Some cache setting or delayed write
>may cause strange thimns to happen. And check Flush in help!
>
>>Hello,
>>
>>I have had several issues with index corruptions and wrong unique keys. Now I have seen that the reason for these problems is how VFP reads the data on the network on two particular machines (XP).
>>
>>The following scenario:

>>*-- Machine 1:
>>USE N:\Cinema\PrimKey
>>?prNumber && returns 11600
>>
>>*-- Machine 2:
>>USE N:\Cinema\PrimKey
>>?prNumber && Shows 11610
>>REPLACE prNumber WITH 11611
>>?prNumber && Shows 11611
>>
>>*-- Machine1:
>>?prNumber && still shows 11600 !
>>

>>In fact, machine 1 does not show the updated numbers, until I reboot the entire computer. After reboot, VFP reads the updated values, but then again stucks on those values until rebooted.
>>
>>Only VFP has that problem, when accessed with another program, the values are uptodate.
>>
>>What could be the reason for that and how can I solve that?
>>
>>I tried SET REFRESH TO 1, Flush IN after every replace, and do record lock (and sometimes file lock) whenever appropriate.
>>
>>Thank you for your help in advance.