![]() Sometimes you want to switch from a Contact to an Invoice and use the cool slide panel for the effect. ![]() It turns out to be great for “Home” and “Dashboard” kinds of views, because often the data for these types of screens comes from many different tables. The Session TO becomes the base for all the layouts you need that don’t have an obvious one. But what if you are building a “Home” screen or a “Dashboard”? What TO do you base it on? The FileMaker Session Model provides a special utility table called “Session,” for this purpose. If you are building a Layout to view “Contacts” you can build it right on a Contacts TO. No Obvious Base TableĮvery Layout in a FileMaker system needs a base Table Occurrence (TO). Although you can assert tight control without it, the FileMaker Session Model is tightly controlled by default. ![]() The user never sees find mode or list view. Typically the developer closes and locks the status area, and puts everything under script control. Since everything is displayed through relationships there is no way for the user to see or edit records that aren’t explicitly made available by the developer. This pattern came to be called the “Session Model”, and this video is an explanation of its key concepts and its pros and cons. Part of that model involved only displaying data through relationships from a central file/table. Way back before FileMaker 7, Colleen Hammersly from Data Waves, and Wendy King came up with something called the “FileMaker Separation Model”. (Thanks to Naomi Fujimoto, you can read this post in Japanese)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |