Custom Dialog Input Not Working?

[fmsavey]

I defined a custom dialog in a script to accept an input field. I clicked on the specify button of "Show input field #1" and chose the field that I wished to popluate via the custom dialog. I gave it a label name and then ran the script. Just as I expected, the dialog appeared with the input field just as I labeled it. I entered the information and clicked on the OK button. I expected to see the data that I entered show up in the field that was was on the layout of the current window. Nothing appeared in the field. I then entered information into the field on the layout and then ran the script again. This time the custom dialog was showing the information that I had entered via the layout. I change the information in the dialog input field and hoped it would change on the layout after clicking the "OK" button. Nothing!! Am I doing something wrong? Did I miss something? Please help if you can!

[comment]

Would it be safe to guess that "OK" is NOT the default (rightmost) button in your custom dialog?

[Ted S]

Greetings,

I believe that I have read on this forumn before that unless you are using the number one (1) button, the change won't commit. I haven't run into this problem myself but it seems like the discussion concluded the the number two (2) button acted like a cancel button no matter how it was labeled.

[fmsavey]

That was it. Thank you for pointing that out. I am still disappointed that I must now use the "default" button. Oh well maybe they will fix this in FM8. Thanks again.

[hellopaul]

It seems that this problem hasn't been fixed with version 8. Shame. I'd been tearing my hair out before I did a search on FMForums and found this answer. I don't want this configuration!

Oh well....maybe in version 9...or 10............!

[Ted S]

I don't think I've ever used a custom dialog in conjunction with a regular field. I always use with a 'Global' field and then use whatever has been entered into the global (via the custom dialog) to populate the regular field(s) based on what button was pushed.

Essentially, the global acts like a temporary place to hold the information until the script can determine which button was pushed.