Actually I tried a test with a Label vs. a TextBox bound to a value. They both refresh at the exact same time. I was just changing a variable in a loop, 1 to 100. The two controls would show exactly the same numbers (like, 1, then 44, then 100, or 1, then 52, then 100). In other words, The choice of control seems to make absolutely no difference.

The way I got them to show each change was to put more code between the time that I change the value and the time that I changed the caption/refreshed the editbox.

I looks like VFP will only refresh so fast. It is almost like it has a refresh request, and it goes along and does other stuff and at some point it checks "Was there a refresh request?" and if the answer is yes, it re-paints the control/screen. In this case, there are several to many refresh requests before VFP asks the "Was there a refresh request?" question. So we miss some of the refreshes. Maybe this is something that helps with the speed of other tasks?

Joe

>>Hi John,
>>
>> One of my colleagues implied wait window nowait techique. After switching to statusbar there was a tremendeus speed advantage. So, I may suggest to use status bar instead of wait windows nowait...
>>
>>>Pretty new card. Shouldn't be too bad. I think that is probably the issue though.
>
>Nadya and Joe,
> Thanks for the help. After more checking I found that the problem is the same on my computer, my laptop and a customer's new Dell computer. The Dell is even worse becuase it is the fastest of them all. It seems that VFP is only refreshing the screen when it feels like it. I am wondering if there is any other way to force screen updates.