Thanks for that tip Jeff.
I've investigate the approach implied by your response. I'm finding grids (in your lingo..) "'ornery critters" :-)


>>>Hi all,
>>>I've got a child grid with all the link, master, relationship properties set up on a one to many form.
>>>Inexplicably, my grid now initially displays all records in the child file, until the master record pointer is moved and the grid is refreshed.
>>>If I move the record pointer in the Load or the Init or in the first Refresh events I still get *all* the child records showing.
>>>If I put a button on the form and its click method is simply "thisform.refresh", then clicking it fixes the display too, but I can't put that in my deliverables!
>>>If I put a timer on the form which does "thisform.refresh" the problem isn't fixed - that's wierd. Why should a button click with "thisform.refresh" behave differently to a "thisform.refresh" in a timer event?
>>>
>>>Strange.
>>>
>>>I've taken to stuffing a next/prior sequence into the keyboard which fixes the problem, but it's not nice. :-(
>>>How can I make it more reliable? It did work before (so yep, I've changed something or other....)
>>
>>Here I am replaying to myself :-). Am I gunna get spanked for that?
>>Anyway, the culprit for the above problem is....
>>The child grid is in a page frame. The activate event of the page does a

>>THIS.grd1.setfocus
>>

If I take that out the grid displays normally.
>>Why do I want a grid.setfocus in the activate event of a page - simple, it forces the record mark to appear on the grid so the user knows where they are.
>>Any comments??
>
>I'm not reading for details here and don't know whether you've solved your problem or not, but...
>
>I believe that there is a bit of problem with grids and child grids and relationships. Even though you might have set up all the relationships correctly, the gotcha is that the Parent workarea NEEDS to be the current or selected workarea so that it can drive the other grids based on child tables.