>>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.
>
>Christian,
>Are you sure you're checking same file on both machines?
>Cetin

Yes, it is the same file. This becomes clear when after rebooting the machine the values are indeed updated. We also do the same without the drive mapping, but with the UNC path.