Hi John,

It's not that I have to leave the subform repeatedly. The user may click
somewhere on the main form during the time entering subform. Also, after the
data entering is finished, double clicking Total textbox on the main form
will trigger the double click event to calculate the total.

On the subform, all of the textboxes are bound, so the data will be saved
when they are entered. But other tables need to be updated after the form is
finished. I want to use a program to do this work.

If there is potential that the update may happen a few time, then I will have
to check the tables to see whether the information has already been there
before doing the update. There may be some better way to do it, please advise.


Guangde

John W. Vinson wrote:
I'm working on this event then I found a new problem. Because what I need to
do is on the subform so I can have the BeforeUpdate event to check only the
[quoted text clipped - 3 lines]
finish entering data. I don't know whether we can have some way to prevent
this from happening.

Possibly; but it's not clear from your post! What constitutes "finishing"
entering the data? The subform must save each record as it goes along; if you
must have certain data filled out on the mainform, and some number of records
saved on the subform, before the entire package of records is "finished", it
can get pretty difficult. One solution is to bind the subform to a
"scratchpad" temporary holding table, and run an append query to migrate the
data into the "real" table when the entire package is complete.

What are the tables involved? Why must you leave the subform repeatedly in the
process? What constitutes completion?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...forms/201002/1