• 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 colorfulempty—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 a 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. Loss of the command buttons isn't a major issue because the form relies on Access macros to filter the detail records.

Loss of all VBA code behind forms is a more onerous problem for automated applications. For example, the Main Switchboard form converts to a page offering a faithful visual rendition of the original object (see Figure 26.15), but the command buttons aren't hooked up. If you've created pages to replace the forms and reports opened by command buttons, add the window.navigate(strURL) method to an onClick event handler for the corresponding buttons.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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