>>>Hi All!
>>>
>>>I've got a pageframe with 3 pages on it. Page 1 contains info from my parent table "SYSTEM", Pages 2 & 3 contain info from my child table "FEATURES".
>>>
>>>My Data Environment for this form contains these two tables with a relationship line joining the two based on systemid. I originally created the relationship with the "OneToMany" property set to True since there are occasions when there are several child records that relate to one parent record.
>>>
>>>All seems to work fine, except that when the user is on Page 1 and is using the navigations buttons to advance to the next/previous SYSTEM record it requires 2 clicks to go from SYSTEM record 2 to SYSTEM record 3. I've figured out that this is because there are 2 child records (in FEATURES) for parent record #2 so it's cycling through both to get to parent record #3. I know this, but I envision confusion for my users.
>>>
>>>If I turn off OneToMany in my relationship, there's no extra "Next" needed to go from 2 to 3, but then I miss the 2nd child record for parent record 2 on my Pages 2 and 3.
>>>
>>>Any ideas on how to handle this???
>>>
>>>MTIA!!!
>>>Mandy
>>
>>This is one of temp relationship liability. If you like to use it anyway, then it's your responsibility to set/reset OneToMany property programmatically (or SET SKIP TO .../SET SKIP TO).
>
>I was afraid you were going to say that... ;^). Thanks for the response!
>
>Mandy

Sorry, I wasn't accurate. It looks that OneToMany property is read-only, so you have to use SET SKIP TO in Page1.Activate and SET SKIP TO somealias in Page2,3.Activate.