Jim ... :o(

I will say this just one more time. I already know that SET REFRESH updates and/or refreshes a BROWS (and I already know that it will update a table) at the SET REFRESH interval.

When you already have a table USE'd (in memory), FIELDS changed by another workstation or program will not be updated. You, at least I had to, will have to issue a BROWS or (USE then USE MyTable combo) to update that field for display.

USE MyTable
Select MyTable
? MyTable.SomeFIELD ... displays "OLD"

After FIELD SomeField is changed by another workstation (REPLACE SomeField WITH "NEW")

Select MyTable
? MyTable.SomeFIELD ... still displays "OLD"

SET REFRESH does nothing for this situation.
On the other hand, maybe I'm missing something ... if so ... please advise.

Mal

>Well I'll be. . .
>
>Just verified that, BUT why isn't that *IMPORTANT* gem right in the header description????
>
>Any normal person, once reading "Determines whether and how often a Browse window is updated with changes made to records by other users on a network." would immediately dismiss this option as not applicable (as Mal, who sounds normal enough to me, seems to have done). When one is looking for a solution, reading to the END of a seemingly useless option is not generally the practise.
>
>Ya know, I am sure that virtually any bit of information "is in there somewhere", be it in the VFP Help or in MSDN. But what real good does it do for anybody when it is buried?????
>
>Cheers
>
>JimN
>
>
>>Mal so as Daniel said use set refresh se the diocumentation on the end you get the following insormation «SET REFRESH can also be used to specify how often data buffered locally on your workstation is updated.»