• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

Q&A

Q1:Is there anything in Hour 9 that bears repeating?
A1: Comment your scripts and focus them on performing a single task. Those two items cannot be stressed enough.
Q2:How do you handle cases in which you need more buttons or data fields than a custom dialog can handle?
A2: One way of doing this is to use multiple dialogs, but that can get tedious both for users and for the person writing the dialog. A more efficient way is to create a new layout that is used as a dialog. If you need to collect data for four fields (one more than a custom dialog can handle), just place those four fields on the layout. Add instructions as well as OK and Cancel buttons. Remember to restore the original layout as part of the script's processing. (And remember that data collected either in a dialog or through a layout might properly go to global fields rather than individual record fields. This is the correct implementation if the data is used simply to carry out a command and doesn't need to be stored with separate values in each record.)
Q3:Can you debug scripts with FileMaker Pro (rather than FileMaker Developer)?
A3: One common way of debugging scripts with FileMaker Pro is to insert Pause script steps. The script pauses at that step, and you can see what the values of data fields are and how the script is operating. It's somewhat less sophisticated than using FileMaker Developer's debugger, but it can get the job done, albeit in a bit more time.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint