If you are using FileMaker Pro 10 have you tried setting up a script trigger that runs a script on exit of your field with the dropdown that simply has a Commit Record/Request [ Skip data entry ; No dialog] set to it?
This might do the trick.
Yes, I am running FM 10 adv and have created a script that: goes to a layout.... does a 'find'... copies the 'description' field to a variable... goes to the last row... inserts the variable into the empty 'description' row... and returns to the original layout. In this script I have inserted Commit Record but it doesn't seem to work.
Sounds like it should do the job, just the act of going to a different layout commits the record.
At what stage is this script run?
Thanks for the reply.
Just to simplify things, I unhooked the script triggers and the problem persists. (there are no scripts running)
You can see HERE the relationships among the tables and that I have a value list that references the NUM field that also shows the value list. It works but I have to click outside the portal, usually to a different layout, to get the NUM value list to 'update'. I have written little scripts that perforemed "window refresh" and "record commit" and attached them to the NUM field 'on exit' but that too did not help. Is this a 'bug' in FM???
Update: It seems that everything works as 'expected'; ie, the NUM dropdown populates with new field values IF I migrate to the next record and then come back to the current record.....???? And 'commit' doesn't work???!?!?!??!
GOT IT !!!
I had 2 fields: NUM and Description on the portal. I had a script trigger (ON EXIT) attached to NUM that when exited did a Record Commit. This DID NOT Commit the record.
What worked was to attach the same "Commit" script (one line of Record Commit) to the Description field on Exit.
It seems that FM updates the record after ALL the fields on the portal are filled in. This begs the question "What if I wanted a field to be blank?"
Oh well.. seems more like a bug in FM.