>Mike:
> You made a good catch, although it didn't solve this problem. It solved a problem that I was going to encounter right after I fixed this one. You are right that I didn't set the Order in the Policy table (a Grandchild table). However, right now, I am trying to fix the relationship between Case (Parent) and mmPolCse (Child). I did set the Order of mmPolCse right after I selected it, and before I set the Relation. Also, the Relation is working fine, but only after I Browse Case and select a record.
>
>Jerry

Better minds than mine haven't been able to help and I have no idea if this will work for you but.......

I've been able to replicate your problem using strictly browse windows.

USE child ORDER ch1
BROWSE
SELECT 0
USE parent
SET RELA TO ch1 INTO child
GO TOP (this does not affect the child browse window)
SKIP (this does not affect the child browse window)
BROWSE (child browse is updated)
&& Close the parent browse
SKIP (this does not affect the child browse window)

If I create BROWSE objects, I can kludge it to work

USE child ORDER ch1
BROWSE
SELECT 0
USE parent
SET RELA TO ch1 INTO child
BROWSE NAME parentbrow NOWAIT(child browse is updated)
parentbrow.visible = .F.
SKIP  (this does not affect the child browse window)
parentbrow.refresh() (child browse is updated)

I don't know if these ideas can be incorporated into your system, but since nothing else seems to have worked so far I thought it might be worth a shot.