Well, there is a page frame, but no search. User enter data for table 1 on form 1, which has multiple pages, save it, and click a button to create a new record in table 2 and fire off form2 to edit the data. The new record is added during the init of form 2. Immediately after the append blank, the foreign key field in table 2 is populated with the key value from table 1, passed as a parameter when form 2 was called.
All in all, it's an annoyance thing, never does the data get corrupted. Probably 90% of the time it works as designed, users get a nice blank table 2 record displayed in form 2 that they can edit and save.
Both forms use private datasessions, optimistic buffering. Good idea to use the coverage profiler, perhaps something wierd is firing in the wrong order.

>Hi
>Are you using pageframes with perhaps some sort of search facility, to look up records already entered.
>Similar problem for me where page 2 (patient details) was the entry page and page 4 (patient Invoices) was a Search page.
>Some objects on page 2 where calling the afterrowcolchange event of the search grid on page 4 (Why I Dont Know) after a new record had been added to the patient file.
>This call to page 4 caused the record pointer to move in the patient detail file away from the added record.
>
>I finally trapped this, using the coverage profiler, noticing events and methods getting coverage when they should not be.
>
>I was using all the usual Buffering, private Datasession, etc
>
>Hope this helps