>Hi Greg
>
>.......The grid may - at its discretion decide that a cell has to be refreshed .........
>
>This is the bit I dont understand. What dertermines this . I have no code to refresh anywhere that I know of anyway.
>Just to re-iterate.. I realise I can code around this but I would like to understand why this is happening
>I could have have up to 40 other forms with similar functionality and dont want to have to change all
> these if I dont have to.
>
>The fact that when I make the screen invisible stops the problem , and also the fact that the records that
> get the problem are random, seems to me that my code is not the issue, but rather something internal to Foxpro , perhaps that it has to refresh the grid every now and again. But why it is doing this I have no idea .
>
>Regards,
>Gerard


Gerard,


I remember having a form with a grid and Dynamic*colors.
Something with a form's method (m.thisform.Method( parameters ))

When I did a createprocess ( run) that comes on the foreground - all Dynamic*colors didn't work any more. I had to code around by returning a default value

In a nutshell the grid does what it wants and when it wants. You can only code 'around' it
In addition - due to the speed of the processor, graphics card, idle times, etc the timing it is not always consistent. It depends on the computer it's running on


It may only refresh one cell (when it thinks it has to). When you scroll done one line for example, it only refreshes the bottom line

Adding 1 to the grid's height re-evaluates all the dynamic properties of all the lines and columns

And there's more I don't know.

So, I take it that the best thing to do is to work around in your case
(1) A view, or (2) have the iif(seek) work on a different alias

Success,