Best Uses for Table View
One of the primary reasons developers cherish FileMaker is the freedom it offers to unleash their creativity within Form and List views. You have the power to craft virtually any type of software you can envision. However, when it comes to Table View, it might seem like you're merely replicating what most end users overuse - spreadsheets. Table View was likely introduced to ease the transition for spreadsheet users into the world of databases. Nevertheless, a well-structured data model renders a spreadsheet-like view of data as useless.
Despite this, the inclusion of Table View comes with some concealed features that can significantly enhance your development process as you create your ideal software solution. This video will unveil all these hidden treasures for you.
Comments
Phantom Fields in table view
I use FM Perception to help manage my solution. I have been analyzing it using FM-P and have found numerous fields that are being reported in the Report Card section as "Layout Objects with Local CSS", some of which are showing as "Phantom Field (Not physically on layout. Available only in table view)"
What causes this with respect to CSS and table views? How to fix it?
Dave17
RE: Phantom Fields in table view
I'm the developer of FMPerception. Hi!
Using the FileMaker table view "Modify" button, you can add a field to the current layout without entering layout mode. This field will appear in the table view (and in the XML for the layout), but will not appear as a field layout object when editing the layout. FMPerception's designation of a field as a Phantom field was primarily intended to help users when a field appears in the definition of the layout, but is not visible in layout mode, and therefore *appears* erroneous. As for how this may impact CSS, I can't help you there. However, with this clarification, some other FileMaker CSS expert may be able to clarify those issues.
No Download files
Hi, could you pleas add downloads links for this lesson "Best Uses for Table View"
Thanks,
Luca