3. What are the three options for the data source of a chart object? Explain how each
differ in terms of the way the data is gathered.
4. What object attributes can be modified in the Objects tab?
5. A developer uses the Objects tab to hide an object so she can work with other objects
on the layout. What circumstances will cause the object to become visible again?
6. A field has a themed style called “Edit_Left” that is set to be left-aligned with 12pt gray
text. What are two ways that this style can be overridden?
7. A FileMaker file has a custom style for a field called “Label_Right”, which is styled as
right-aligned, 10pt, and red. The developer wants to use this style on another layout, so
he copies the object’s style using the Copy the object’s style button and selects
another field on another layout. He uses the Paste a style button. What happens?
8. A phone number field on a layout needs to have a script trigger on it that checks to see
if the field contains an entire phone number in the proper format. If the user enters
“2123” in that field, how can you set up the script to prevent the user from leaving the
field and saving the data?
9. List the order in which these object script triggers run: OnObjectModify,
OnObjectEnter, OnObjectValidate, OnObjectExit, OnObjectSave.
Answers
1. In FileMaker, context refers to the underlying table occurrence of a layout, the current
found set, and the current record. Almost every action in FileMaker operates from the
current context, so if the context is incorrect, you are likely to get unexpected results.
For example, consider a script intended to delete a Student record. The Delete Record/
Request script step will simply delete the currently active record, so if the script were to
run while the current context was a teacher or class record, a record in the wrong table
would be deleted. You can change or check the current context using a variety of script
steps, including Go to Layout and Go to Related Record.
2. In this scenario, you would only see the first related ContactMethod for each related
contact. For John Smith, it would show only cell phone. To view all of ContactInfo
records, the portal’s context would need to be changed to ContactMethods. This action
would result in all three of John Smith’s ContactMethods records being visible in the
portal, as well as all ContactMethods for all other company employees.