>Justok, the first reason is the data integrity. This way ensures that all code you specify in QueryUnload() for each opened form for proper closing is fired. Usually, in QueryUnload you check if the record was changed, and if it was it asks user if he wants to save the data. If YES the Form.onSave() method fires Form.Valid() method, which validates the record. What you suggest will work in simple cases, but in general it does not prevent the wrong data from getting into your tables.
>
>The second reason is that not neccesarily all the changes made by user in several opened forms have to be changed. This code leads user through each opened form, reminds about changes made and leaves the final decision for SAVE up to user.
>
Well put, Nick...this is exactly my situation :)