Hi,

I'm using a multi-occurence form and one field that is part of my index is only display.

When i add.set the field is initialize correctly and when i finished entering the record i want to be able to save record and force another add.set.

I tried to do an execute(update.db) on the after.input or after.field of the last field on the occurence, but this not allowed.

Where or how can i do it ?

Thank You,

Never tried this myself. How do you know they are at the last occurence? I mean they could input 6 or 10 or even 20 records? The thought that crosses my mind is they hit the save button. That saves all the data and then you could try to force it to execute(add.set). Is add.set what you really want? Or is it start.set?

The add.set is what i want, but i would be able to do the save data automatically instead of pressing the Save button.
I mean do the save after i added a record.

So you want to force a save after adding one record correct? You can try the before.display on first field - execute(update.db), execute(add.set). Wish my help worked on the windows 2007 laptop - but I can't get into my old help files, Plus I can't even add programs to read it.

Hello,
I think that on after.field section of the last field, you should call commit.transaction() because the record is already locked.
Then in the section after.update.db.commit: call execute(add.set)

choice.update.db:
before.choice:
whatever you have here

after.update.db.commit:
execute(add.set) |this will be called each time a commit was done

Just thought of something - how would you ever get out of insert mode? In either solution.

Got it - you could set a flag for when a user hits insert or add.set, as long as the flag is on you keep doing execute(update.db), execute(add.set). Then when they hit save it turns the flag off and skips the execute statements.

yes, this is also how I thought about. On choice.add.set or duplicate.set set flag automatic.add = true.

On the choice update.db: set the flag on false

Then. in after.update.db.commit: