>I know the feeling when things don't go the way you want it ..
Well, we aren't programmers for nothing...:-)

>Is the LockScreen still in the load and reset to FALSE in the init of the form ... may help
Yes, it is

>Also, cann't you select the subset - in the form.load() - into a cursor (or work with a view) and have that as the recordsource of the grid ?
Of course i can. I generally never work with the table itself, but rather use parameterized views for that, where i requery the data only when needed, etc...The thing is that for this case it seems like an overkill. I thought to go for this option if the result of all the playing around wasn't satisfactory enough, but luckily it seems ok for the client now...

Jaime

>
>All small pieces may help
>
>Gregory
>_
>
>>That is the case exactly. Still, i tried moving the pointer in the Load method ( of the parent, the child, the grand parent, my neighboor's parent and child ) , and it still does the same, although i have less data flashing now ( even in a slow workstation ), so for now the problem is solved, but still, it's quite frustrating...
>>
>>Regards,
>>Jaime
>>
>>>Jaime,
>>>
>>>That may well be it if there are relations involved and the grid has a linkmaster
>>>
>>>Success,
>>>
>>>Gregory
>>>__________
>>>>Gregory
>>>>Nope, as i said, i tried playing with lockscreen and refresh, but still no go. My feeling is this has to do with the data. I am going to try to move the pointer in the parent table (customer) prior to drawing the grid, so this way i am sure the data is set up prior to the control...
>>>>
>>>>Thanks
>>>>Jaime
>>>>
>>>>>Just a thought
>>>>>

>>>>>form.load
>>>>>this.LockScreen = TRUE
>>>>>
>>>>>Form.Init
>>>>>=DoDefault()
>>>>>=this.FirstControl.SetFocus()
>>>>>=this.Refresh() &&  or this.Grid.Refresh() && maybe optional
>>>>>this.LockScreen = FALSE
>>>>>