I have a question concerning the general behavior of relationships in the data environment. When scrolling through records in a child table, if I have set the realtionship in the datanvironment, the parent table changes records accordingly to the record whose key field matches the foreign key value in the child table. When appending a record to a table and filling out a form, a few of my routines use a listbox, grid or choose screen to choose records from a parent table. Since merely filling the values into the foreign key fields in the child table isn't enough to move the pointer in the parent and therefore show the correct values for other fields after a screen refresh, I have been in the habit of doing a SEEK after the parent record has been chosen to position the parent pointer accordingly. This has worked fine up until now, when I am having problems getting the whole business to work correctly. Some of my problems have hinted that I don't quite understand the mechanism. One of my forms calls a quick little lookup form to choose a parent record. After choosing the record and doing the SEEK on the parent table, the child (main) pointer moves! My question is, what specific event triggers the change of record position in the parent table? Why does a SEEK on the parent table cause a relocation of the pointer in the child table? WHAT'S GOING ON? Thanks in advance for sharing any wisdom.

Erik