Add and remove fields in Browse mode
The first new thing you’ll notice when looking at a layout which is set to display with Table view is the Modify button, located at the right edge of the Status Toolbar. The Modify button displays the Modify Table View box, which allows users to add or remove fields from the view, or use the traditional double arrow icon to reorder the columns in the view. All of this occurs without leaving Browse mode.

Fields no longer have to be physically on the layout in Layout mode to be displayed in Table view. Fields that are actually on the layout display a small padlock in the Modify Table View list, and while you can turn them off, they cannot be removed permanently from the list.

Fields that are local to the table upon which the layout is based or fields from related tables can be added to the Modify Table View list by clicking the green plus sign and selecting the appropriate table occurrence. Once they’re on the Modify list, the checkbox can be used to display them or hide them in the Table view. Any fields that do not have a padlock icon next to them can be removed from the Modify Table View list by selecting the field name, and then clicking the Trash can icon.

Show summary parts in Table view
The ability to create Dynamic Reports is another important FileMaker 10 feature that extends the power of Table view. Dynamic Reports give developers the ability to add summary parts to a traditional list view, thus allowing users to view summarized and aggregated data without entering Preview mode. This same functionality can be extended to Table view.

Unfortunately for power users, a developer still has to set up the summary parts in advance, but once they’re in place, they will display by sorting by the correct fields. Since Table view comes with automatic column header sorting, viewing different groups of data could be as easy as clicking the appropriate column header.

Proceed with caution
If you are a developer and your users have the ability to view a layout using Table view, they can now access fields that may contain sensitive data. If you previously prevented access to certain fields by simply leaving them off of user-accessible layouts, you need to revisit your strategy.

Preventing access to sensitive data should be handled at the privilege set level in the Manage Accounts and Privileges module of FileMaker. Developers should never depend on layouts to prevent users from accessing fields that contain sensitive data.
If you have any questions about this tip or have ideas, suggestions about other topics to explore, please contact me at jason.mundok@itsolutions-inc.com or 866.PICK.ITS. Visit us at www.itsolutions-inc.com.