>from the "Bible" ;) :
>"A BROWSE shows a number of records on the screen at any one time, but other users might be changing those records as you watch. If REFRESH is left at its default state of 0,5, these changes are never displayed. For table fields displayed with other controls, you must lock a record to be sure the fields display the actual values stored on disk, but REFRESH can "read through locks" to show you the most up-to-date information available while within a BROWSE.
>
>The second parameter is less well documented. This parameter supposedly determines how often the locally cached data buffers should be updated with new data. Don't ever set this parameter to zero, or you won't see changes made to records displayed on screen until the records are locked.
>
>It seems to us that the default setting of 5 seconds should beat the server to death with so many requests to update data that the entire system would come crashing down, but that hasn't been our experience. On very large systems or WANs where network bandwidth is a precious commodity, we recommend you try raising the refresh level by doubling it and checking the performance change to the network and application. Ten, 20 or even 40 seconds between updates might not make that much difference in the appearance of your application, but could significantly affect other network performance criteria. As always, your mileage may vary; test your application under your environment to be sure of optimal performance."

Jean, have you settled on a common SET FRESH TO command? Curious what you and others are using. Thanks.