On RDS I have seen this, but never on physical machine - that was reason for hint on driver.
On RDS heavy handed stuff like form move, or form hide and show sometimes cleared such issues up - not that they happened often, but for long running remote tasks every 5 minutes I included 1 such a call to verify by quick look if screen was "rather current" together with a "cleanup" call.

With older IE minimizing/restoring window helped a lot - but that was probably linked to the "other memory" WorkingSetSize pruning, as IE when roboted gobbled up memory like crazy. But Minimize/Restore cleaned both up... W2K and XP days with IE6 and younger me ...

>>Neither watertight nor consequent - select ("sometable") but skip in ("sometable") something is too much... still
>>>The code is not called in a function. Here is a simplified version:
>>>
>>>

>>>select ("sometable")
>>>cTotal = " records already done of " + str(reccount("sometable")) + " records"
>>>iCount = 0
>>>go top
>>>do while !eof()
>>>     iCount = m.iCount + 1
>>>     wait clea
>>>     * DoEvents  && should NOT be necessary
>>>     wait nowait  str(m.iCont) + m.cTotal
>>>     *--- something happens to the record in "sometable"
>>>    select ("sometable") && as eof() works on workarea and "something" might affect it 
>>>     skip
>>>enddo
>>>

>>
>>or add in clause to go top and eof(), but don't mix. Your code misses benefits from either approach, only has problems of both. Still, the Wait Clea line ***should*** be enough, unless screen driver has a problem, as it removes prev hint.
>
>It seems like some form of "caching/queueing" of screen updates is happening (i.e. screen updates go to a "frame buffer" which may not be immediately "flushed" to the actual display) -- sometimes a DOEVENTS might help to "unstick" this -- though if your program is running through a remote desktop, the problem will still problem occur).