Specify button...Perform Script - not working

[Dana G]

I'm sure this is easy. I am just missing something.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[color:red]Basic info: I have a "home" layout which displays buttons for certain layouts in the file. When the user clicks a button they need to be taken to a specific field on that layout. Button in question is named "Utilities"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

"Utilities" button is specified to:

"Perform Script ["Home_P1_Utilities_button"]

"Home_P1_Utilities_button" script is written as follows:

Go to Layout ["Phase One Report_Pages 12-20"]

Set Zoom Level [150%]

Go to Field [Phase One_ISV::utilities_tsu_exist}

Commit Records/Requests []

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The button, when clicked, does not complete the script. It completes the 1st step and takes the user to the specified layout.

When I manually run the script via Scripts menu it works perfectly.

What is happening that it will not work when specified to a button?

[Reed]

Can you post the file?

[VICH]

i think i see whats wrong...there is no pause in your script....you go to layout...zoom...goto field...then commit....there is no break...to me it looks like you button works just fine...if i understand correctly commit takes you out of an active field

[Dana G]

This may be a stupid question but how do I attach files? What format would you like?

[Dana G]

thanks for the response...

OK that makes sense but why then does the script work perfectly fine when I select it from the Script menu on the toolbar?

Is there an easier way? Does FM have a Go to Page step that works in Browse?

My end intention is to use the buttons to let the user navigate to pages 2, 3 and 10 of a layout that is 11 pages long.

[Reed]

When you create a new post or reply, there is an option to attach files. Typically people create a .zip archive of their .fp7 file with the passwords stripped out, and attach that. Then others can see if they can reproduce the problem, and try to debug it, or find a workaround.

There really isn't a concept of pages in browse mode...