entering Parent and child record at the same time

[GGandhi]

Re: entering Parent and child record at the same time

hello

will a transaction table with children tables work in this scenario?
the form and browse are based on the exact duplicate of the original tables in consideration. and when save button is pressed in the form extra code is written to open the real table and append the information to the master table with children tables.
delete or cancel button will delete the child or cancel edit on the child table in the transaction tables only leaving behind a parent with out a child.

In Alpha, like life, there can't be a child until there is a parent to whom it is related. Additionally there are parents who never have children.

this will be true only for the transaction table.
is this possible?

[Ray in Capetown]

Re: entering Parent and child record at the same time

That was also my thinking Tim - however it just struck me that there's a real easy technique simply using the inherent behavior of linked embedded browses.
John you can try this out.
Make the new PO master with link field set to a value that will never be used as a PO number - lets say "9999999"
Give your user access to change that number IF it has a value of "9999999". Allow them to add child records. If they add a child and this will become a formal PO, a button that exists only for "9999999" to SUBMIT this as a PO will then simply allocate the formal PO number to the master, the children will remain attached to the new number and no longer be able to eliminate the PO.

"9999999" becomes a scratch PO that is ignored for all other purposes. No coding nor fancy footwork except for the conditional options to submit it and prevent further change of PO number

If there is a possibility of multi user collision then it gets a little complicated, use either shadow tables or temp table names based on user id perhaps.