Prior to FileMaker 13 you would use tab controls to create a dynamic view, a section of a layout that changes based on some condition or action. The premise was simple: name each tab in the position section of the inspector set the width of the actual tabs to 0 pt From there you could control which tab was presented to the end user with the Go to Object script step. This worked well enough but the maintenance was just a little bit laborious since you would either have to activate the specific vi
TIP: In many pickers, we use a global variable to store the selected records in the found set. When clicking a record, the id is stored in the global variable. Then we use conditional formatting to highlight the lines selected. Unfortunately there has to be a 'pricy' refresh window script step for the conditional formatting to take place.
This a major update to Master Detail 1.0. New Features MasterDetail Portal Record Limit MasterDetail now detects the number of records in the MasterDetailRows table, and constrains the found set based on that number. If there are 1000 records in that table then a max 1000 records will be found. There is intelligent messaging displayed to the user …
Easy to use. • Create and modify drawings directly from within FileMaker. • Uses familiar drawing tools, including pencil, eraser, line, text, and more. • Save your work to FileMaker container fields (as png or jpg files). • Use existing drawings as backgrounds, and draw on top of them.
Easy to integrate. • One table, one layout, and a few scripts. • No need to make changes to existing tables. • No need to make changes to the relationship graph. • No need for additional databases. • No need for plugins.
Charts are great visual tools, but they can quickly get messy and difficult to read. A chart that compares sales of different products throughout the year would get very unreadable if all the products were listed for all the months of the year.
The point here is that FileMaker uses its field names as column names in Excel export. There is no way around this. For related fields, FileMaker shows the fully qualified field names, such as “TO1_TO2::Field2” which makes most users go crazy.
FileMaker Inc. has identified an issue with keyboard shortcuts on FileMaker Pro 13 and FileMaker Pro 13 Advanced running on OS X Yosemite. When performing the scenarios below, some shortcuts stop working and the command is removed from the menu (see image below).
In the framework is the idea of a print job. Because RoboPrint runs in FileMaker Pro, and RoboUser can be on any platform, there needs to be a method of communication between them in order to convey the type of report RoboUser wants to run, and any criteria around running it. We do this by way of a table funnily enough also called RoboPrint (just to confuse you!).
In the current build, all that's required to wire up EasyWeb to a database is to point EasyWeb at the database (provide EasyWeb with the server address and the name of the database), add a few layouts to the database, and you're ready to go.
Simple database systems may be easily contained within a single window, but you don’t have to get too terribly complicated before popping a new window makes a lot a sense. Whether it’s an off-screen window for creating a related record or a specialized dialog box to guide a user through a tricky process, the single window interface isn’t always practical. But with the flexibility of multiple windows comes the responsibility of managing them.