To flesh out this answer a little more...
Often, when there is a need to save data in several tables all at once (such
as a master and details), it's best to have some kind of batch posting
mechanism, so the data is entered into a staging table or with a pending
status, then, when a Post action is requested, copy the data into the
permanent table, or remove the pending status flag on the master record for
the entry.
There are side benefits to this approach, including the fact that a user can
leave an entry 1/2 done, close the program, come back later, finish it, and
post it. This scheme can also overlap with other useful business metaphors,
for instance, a pending order can double as an estimate.
On 18 Feb 2005 17:30:59 -0800, "Barry-Jon" <ba**************@yahoo.co.uk>
wrote:
Using an embedded subform when you leave the subform it loses focus and
the (sub)record gets saved. You might consider using temporary tables
to hold the data (the save still happens but to the temporary table).
You could then take whatever additional actions you wanted to take and
depending on whether or not you wanted to commit the changes you could
explicitly 'save' the record to the permanent tables using code or an
update/append query.
