You’re right though … there’s definitely more than one way to skin a cat, eh?

PassParameter( "objectName" ; GetFieldName( TEST::field_Pregnant )

That way you don’t have to worry about the names of the fields changing.

I still believe it’s a little cleaner to do it in one centralized script because you don’t have to go to each individual field to figure out where it goes. I think at this point it’s more of personal preference though. Thanks for the comment.

We are actually going to be writing a post about using a script much like the one you just wrote for copying entire records into hashes and passing them around.

Script: GoToObjectOnKeystroke [objectName]

Script Steps:
Go to Object [Object name: #P ( "objectName" )
Exit Script [Result: False]

I hate long branching If, Else If branching scripts. I much prefer to put the logic right into the field’s script parameter so I can see all of my layout logic without having to go back to ScriptMaker. In addition, you now have a single script which can be used for your entire solution.

You should probably create two custom functions (e.g., IsKeystrokeForward, IsKeystrokeBackward), which trap for the shift modifier key for a backwards tab.

The Script Parameter wold look like:

Case(
Self = “F” and IsKeystrokeForward ;
PassParameter( “objectName” ; “field_Pregnant” ) ;
Self = “F” and IsKeystrokeBackward ;
PassParameter( “objectName” ; “field_PriorFieldName” )
Self = “M” and IsKeystrokeForward ;
PassParameter( “objectName” ; “field_ProstateExam” ) ;
)

Of course you’ll have to assign object names to the fields in question, but I think it’s worth it.