You're welcome!

As a suggestion, you should seriously consider using parameterized views in getting recordsets instead of conventional SET RELATIONS or relating tables via DE. This way, your app will be ready for C/S and will significantly avoid weird behaviours.

>Thanks Jess!!
>
>It was something silly (number 2)... one of the page frames was refreshing another child and never reset the alias back to the the form.dataenvironment.initialselectedalias (the master). Sometimes, another set of eyes helps...
>
>Ric
>
>>Guess:
>>1. the child index key (relating to the parent table) is no longer the same when you first invoke the form. Check somewhere in your code which you changed the child index.
>>2. make sure that upon refresh, your selected alias is always the parent.
>>
>>>Hi Everyone,
>>>
>>>I have been watching and looking for a similar problem which has come about - similar to that of Thread 645455. However, here is the situation (I must really be missing the boat on this one):
>>>
>>>Simple form. DataEvironment has three tables - Master, Working, User. Relations are set: from Master Into Working based on Working.Number, from Master INTO User based on Working.UserID. Both childs have the proper orders set.
>>>
>>>On the form... 3 pages from a single frame. Under the frame, not part of it, is a tbx with User Name, from the related user table. On page 3, a field which should show the Working.WorkTitle, from the relation Working.Number.
>>>
>>>WHen I start the form, both child tbxs are fine. However, moving to the next record in the Master Table - the user name box refreshes; but the Working.WorkTitle does not. I ran several debugs, and finally realised the pointer in the child Working is not moving. It should move in relation to the Master but it is not.
>>>
>>>I have no other SET commands on the form (or any classes); nor do I change the alias from the Master. So, any suggestions?
>>>
>>>TIA
>>>
>>>Ric