Hi Dodi,

Sounds really similar to a problem I ran into with tableupdate and row buffering. Message #460295 Have a look at the child table on its own without an order after you have done the steps to create the duplicate image, and then set the order to the index used in the relationship and look again. If the duplicate row shows up when browsing the table when ordered by this index, but doesn't show up when not ordered then it sounds like the index is hooped. Reindex should repair it.

My problem happened on a single table when two users were editing the field that the table order was based on at the same time and the second user forced an update. The behavior, the whole phantom row thing, was identical. On your form can users edit the field that is used in the child index for the relationship? What kind of buffering are you using?

Bill

>I'm at wits end.
>
>A simple form - parent & child (without grid) for new add's of Sales Employees:
>
>Parent: Employ (employee serial number, first & last names, hire date)
>Child: EmplDtl (salary, salary effective date, manager number, sales quotas, etc...)
>
>A form consists of Employee S/N, names & hire date, bound to Parent Table, and salary, salary date, manager, quotas, bound to Child Table. After the Parent fields are entered and TableUpdate successfully, Child fields are enabled for entry. cmdSave (TableUpdate) saves the data into Child Table. The form works fine.
>
>After the entries are successfully saved into the tables, I checked the tables. All looks fine. But when I set the relationship between Parent & Child, browse both tables, there is a duplicate grid row in the Child table (same record number). Strange behavior. Only the first row is editable, the duplicate row below it isn't. Changing a value in the first row would also reflect in the duplicate row below it. Why is this happening? I also have another form for these tables with grid to display child records as history. It would also show the strange behavior. Only if and when I pack the Child table would the problem go away! Why is this happening?