In Layout mode, you can see how this layout comes together. You can also see the date the report was printed in the top-right corner, and a page number at the bottom of each page.įigure 5-12. Notice it's formatted to fit nicely on letter-sized paper when printed (it's in Preview mode here). ![]() This is the report you'll add to the People database. To see your layout in Preview Mode, choose View images/U2192.jpg border=0> Preview Mode.įigure 5-11. You can see the report in Layout mode in Figure 5-12. The body is the most important part: It has all the fields that show your information. The header includes a title, the date, and some column labels, and the footer has just a page number (these parts print on the top and bottom of each page). In the spirit of visualization, how about a picture? From the Preview illustration in Figure 5-11, you can get a pretty good idea of how this layout is going to come together. When you create a detail layout, you're free to make it large or small, tall or short, narrow or widewhatever meets the needs of your data. This step is especially important when you create a report, since the physical constraints of a piece of paper often dictate the working space you have. The next chapter will introduce FileMaker's powerful data summarization and reporting capabilities.įirst, you need a rough idea of how your layout should look. But FileMaker's reporting powers go far beyond simple lists. ![]() You can then file the printed list as a hard copy backup, take it with you on a trip, or mail it to an associate. In this chapter you'll create a report layout for a simple purpose: printing a list of people. The People database needs a reporting layout, too. Almost no database gets by without some kind of a report layout, and most important databases have several, from straightforward lists to powerful snapshots of your data's important statistics, like sales by region or inventory by product category. But report layouts are designed from the ground up to be printed. A report's no different from any other layout as far as FileMaker is concerned. ![]() ![]() You also want to do reporting, an equally important task in a typical database. Layouts like these meet many typical database needs: You've got your detail layout for finding and viewing individual records, and your list layout for rapidly scanning many records at once. You've now knocked out two good layoutsa detail layout (Chapter 4) and a list layout (this chapter).
0 Comments
Leave a Reply. |