>I set the OneToMany property of my parent/child relation to true. This will move through each child record before going on to the next parent record. This works fine when you are moving forward. If you are moving backwards, however, only the parent records are being traversed. So , if my parent were made up of "household items" and child of "parts" moving forward I would see: Chair,wood,screws,plastic Table,legs,bindings,lacquer Computer,cpu,motherboard,memory. Moving backwards, however I see: computer,table,chair...completly skipping the child records. So, moving forwards took 12 clicks on the next button to get to the bottom, but moving backwards took only 3 clicks to move back to the top. (Yea, it was a lame example, but I'm doing it on the fly ya know :-P).
>
>There's probably a good explanation for this, but darned if I know what it is.
>
>
>Michael G. Emmons
(Spam, spam, eggs & spam) - Sorry, couldn't help myself
Check out the "SET Skip to ....." command. I just set up a parent/child, browsed it and did a bunch of SKIPs and SKIP -1s. Worked fine.
First you set the relation between Parent & Child, then set skip to
.
HTH
Barbara
