Michael,

>>I end up skipping to the next record in the child table instead.
>
>That is how the relation is supposed to work.

Considering the word I put in bold, it sounds like the parent record is NOT skipping, but the child record is skipping INSTEAD. Why do you say that is the way the relation is supposed to work?

If he has SET SKIP TO childtable, it should work that way, but normal relation should skip in the parent record and point to the first child record matching.