After you have created a number of reports, you might notice a problem or two cropping up from time to time. Many times these fall into the main areas of ...
- some data entry that is goobering up your reports
- some interface elements that are goobering up your reports
- some of the scripting for your reports is goobered up
DATA ENTRY PROBLEMS
The most typical are missing data where it needs to be or data that needs to be consistent and it isn’t.
For example, your report might count a number of records and then calculates a percentage total of the overall records. In a case like this, empty or duplicate records might throw your actual reporting values off.
In the case of empty values in sub-summary reports that sort upon that field, those records will be grouped together. So you will have a hole in your report that can be open to interpretation by your report audience.
In regards to data entry that should be consistent but is not ... consider a report that sorts by a state field to give sub summary totals broken down by state. If one user decides to enter in Washington instead of WA, the totals that should be in the same grouping are not. This can happen when users are copying and pasting information instead of typing it in correctly.
INTERFACE ELEMENT PROBLEMS
The most typical problem is when a layout object isn’t fully in one layout part. If a field, for example, should reside in a sub-summary part but a small bit has strayed into another layout part, your report will be goobered up.
Another new problem can arise when a developer copies layout fields from one layout and pastes them into another. It is possible those fields have FileMaker 9 object anchors that move those objects in ways you didn’t intend them to on the new layout.
PROGRAMMING PROBLEMS WITH YOUR SCRIPT
The most typical problems come from ...
- a search that doesn’t match the report needs
- a sort that doesn’t match the report needs (break fields)
- the script is on the wrong layout at a key moment
- the script isn’t in preview mode (for sub summaries viewing)
In most cases, these problems happen with you do a last minute tweak to the report or the script without testing. Generally, you can find the problem quickly by using the Script Debugger feature in FileMaker Advanced.
More info about the author and FileMaker in general, contact me at firstname.lastname@example.org.
© 2008 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.
====================== ADVERTISEMENT ==============================
For more information on the InBizness SOHO and other quality FileMaker framework solutions, please visit http://www.dwaynewright.com/solutions.html