Why don' t you use the ExecuteSQL instead of making all these relationships with zNAV? One ExecuteSQL function on the button name and another in ScriptParameter. Much easier? Or?
I like that idea. I am sure I just didn't think of it, though the expressions are quite simple. We could use this expression for the first button's label: ExecuteSQL ( "select Label from zNAV where \"Order\" = 1" ; "" ; "" ) And this for the first button's script parameter: ExecuteSQL ( "select Destination, \"View\" from zNAV where \"Order\" = 1" ; "¶" ; "" ) For the other buttons, just increment the number to 2, then 3, etc. I would probably change the names of the zNAV fields View and Order to names that were not SQL keywords so they would not have to be wrapped in escaped quotes, just to make the code prettier. I cannot think of anything else that would break, can you? Thanks for the great idea!!!
@@AccelerateComputerTraining it is funny that you did not think of it - I watched your executeSQL video and applied it because of your tutorial....I just call the field "Layout order" no trouble with SQL. In the script parameter of the button I also use executeSQL, very simple and crisp.
Why don' t you use the ExecuteSQL instead of making all these relationships with zNAV? One ExecuteSQL function on the button name and another in ScriptParameter. Much easier? Or?
I like that idea. I am sure I just didn't think of it, though the expressions are quite simple.
We could use this expression for the first button's label: ExecuteSQL
(
"select Label from zNAV where \"Order\" = 1" ;
"" ; ""
)
And this for the first button's script parameter: ExecuteSQL ( "select Destination, \"View\" from zNAV where \"Order\" = 1" ; "¶" ; "" )
For the other buttons, just increment the number to 2, then 3, etc.
I would probably change the names of the zNAV fields View and Order to names that were not SQL keywords so they would not have to be wrapped in escaped quotes, just to make the code prettier.
I cannot think of anything else that would break, can you?
Thanks for the great idea!!!
@@AccelerateComputerTraining it is funny that you did not think of it - I watched your executeSQL video and applied it because of your tutorial....I just call the field "Layout order" no trouble with SQL. In the script parameter of the button I also use executeSQL, very simple and crisp.
It would even better if FileMaker could pull the icon from a container field!
That would be great! Thanks for watching, Vinny!
@@AccelerateComputerTraining we can wish…