![]() This exposure is essential for a developer’s sanity, efficiency in tracking down issues, and lean & well-organized custom apps. After running a DDR and processing it in some way, I can find the exact places the field “zz_AccountName_g” are used (if any). The FileMaker Database Design Report is meant to expose the DNA of a custom app, clearly identifying the locations and uses of fields, calculations, layouts, themes & styles, scripts, and other pieces. The FileMaker Database Design Report helps us to find that which we forgot. ![]() I might have created a field called “zz_AccountName_g” and used it throughout, but months later, I cannot remember where I used it or even if I ever used it in a script or on a layout or in an privilege set. But as the custom app grows in functionality, data-storage, user-interfaces, it is easy to lose track of some part of it. ![]() The web these pieces creates starts simple in the first stages of development and we may even be able to keep it all in our heads. Every custom app we build is a complex DNA strand of tables, fields, layout object and scripts, security privilege sets, conditional formatting, data-formatting options, relationships, calculations, indirection sources, and other attributes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |