• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

Saving Forms as DAP

The ReportML transform isn’t named FormML for a good reason—saving forms as DAP has severe form design limitations. Most forms have subforms, tab controls, or other objects that ReportML ignores. For example, saving Northwind.mdb’s sample Employees form as a page results in colorful—but empty—Caption: Employees and Header: Employees sections. Saving the Customer Phone List form creates a page with elements for the form header, detail, and footer section. The Caption section has an extra line of field-name captions, and the 26 command buttons to filter the records are missing from the option group below the navigation control (see Figure 25.15). Loss of the command buttons isn’t a major issue because the form relies on Access macros to filter the detail records.

Figure 25.15. Saving to DAP forms that generate simple lists usually works, but you must tweak the page design in most cases.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint