When using form 2 or 3 with n occurrences, sometimes when the last occurrance is completed, the cursor moves to the first occurrance without updating the set. When this happens, the user may not observe this behavior and user is modifying data which has not been written to disk.

Sometimes, the table is updated and the process continues to insert a new record which is the first occurrance of the next set of records.

What controls this?

Would something like this work for you? I used something like this in one program. I am not sure - some events you can try debugging to see if they hit it. I am not really sure since I have not seen this problem - yet.

form.all:
after.form:
if update.status<>add.set or form.curr = 3 then
execute(update.db)
endif


or I have done this

choice.modify.set:
after.choice:
execute( update.db )