>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
>
>(snipped)

Hello Bill,

I was finally able to quench this problem by using just views! Thanks for your input & help, tho.