>What happens if you replace thisform.refresh with thisform.lbl1.refresh?
>
>My thought is that since the SQL is called immediately after the form.refresh, that the SQL is executing (and hogging resources) faster than the form.refresh. A single control refresh might be more efficient.
>
>If that doesn't work, then i'd try the work-arounds.
>
>FWIW, you could put the .lbl1.caption="running.." and lbl1.refresh INSIDE the .RunSomeSQL method. It's a more modular design, so that the label is updated correctly regardless of where the method called. Even if it's only called from one point, it might correct the refresh problem (because the commands would be sequential inside the same method??) HTH

Labels don't have Refresh methods. Refresh is used by VFP to reassign the Value property to the underlying ControlSource value. Since Labels don't have a ControlSource property, it doesn't have a refresh property.

Note
Some frameworks add a Refresh method to controls that don't have them because its used for other purposes (e.g. changing the visible property based on security access).