>Hi all,
>
>I recently stumbled across a setting that solved a long-standing (although very intermittent) problem. I realized that the framework was setting SET REFRESH TO 0, 60. SET REFRESH must have changed over the years or else I just never looked at the command that closely - I only assumed that it affected using BROWSE/EDIT on a network table and so I had my default set high (first parameter set to 120).
>
>Once I reset this value to something a lot lower for the process with the problem (a server based process that checked for user submitted records), my server-based process worked correctly (I set it to 15, -1 [always read from tables, not the buffers]).
>
>So that process running on the server is now fine. But now wondering what others would recommend for a general setting for the users - users have reported the odd, very-rare instance where when they save and close a form that if they go right back into a form, it does not always show the data correctly. The help file indicates that this setting is primary for when a user is looking at a record on the server that someone *else* might have changed - I don't think it should affect users ability to see changes they made themselves? Or are forms with private data sessions affected such that if they save data in one form that it is not seen by another form for a period of time.
>
>Interestingly, when tracing through to find where this setting gets changed by the framework, the value of the 2nd parameter for SET("REFRESH",1) would change to zero whenever code fires that was in a procedure file (the procedure file does not have this command in it anywhere) meaning that somehow the procedure file code "lives" in its own world...weird.
>
>So anyhow, what do others set this to? Has anyone set it really low (perhaps 5,5) and then found that this generated too much network traffic or slowed performance of the user's client app?
>
>Thanks,
>Albert

Hi Albert

MaxFrame has a function x3rlb.prg which you can use to force a refresh of one particular alias on demand. I have found this to be more efficient than changing set refresh which affects all tables.