Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Server / refresh problem
Message
From
02/10/2006 10:05:08
 
 
To
02/10/2006 09:54:25
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01158536
Message ID:
01158544
Views:
40
When viewing on the first machine, the value stays the same, even if I close VFP and open VFP again. It also does not make a difference when moving the record pointer.

I do FLOCK(), replace the value, and then UNLOCK the file. This particular code is the generation of the primary keys which always works for years already on thousands of computers and hundreds of networks. But it has nothing to do with that particular code:

This exact same behavior is not only with Tables, but also with files ("test.txt") that are created on the network share. ?FILE("test.txt") returns .F. until rebooting the machine. Viewed in Explorer, the text file can be seen, but VFP cannot "see" that file.

Another computer (W2K) on the same network does not have this problem. It is just the two computers that do not see the udpated values or files.

By coincidence, these two machines are both XP, but it may have nothing to do with it.

>Christian,
>
>See below.
>
>+ you have to rlock the record before updating it
>
>>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:
>
>go (recco())  && what does it print now ???
>
>
>>?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 Isberner
Software Consultant
Previous
Reply
Map
View

Click here to load this message in the networking platform