In the Real WorldEnhancing Data Access Page Design

In the Real World Enhancing Data Access Page Design

Much of the content of this chapter concentrates on the lack of support by DAP for common Access form and report designs and control objects. Observations about Save As DAP features that work as expected might be classified as damnation by faint praise. There are workarounds for unsupported objects such as subforms and subreports but most workarounds aren't elegant, require VBScript programming expertise, and often need additional HTML code. In most cases, what you see in Access isn't what you get in pages without a considerable amount of work on your part. Bear in mind, however, that creating a datasheet-style data entry Web page, for example, isn't a piece of cake in any authoring tool. This is especially true if you need to implement the equivalent of the Undo, Sort..., and Filter... buttons of the navigation control.

Third-party Access developers have the opportunity to improve on the basic functionality of the Save as DAP feature. For example, Michael Kaplan and Julianne Lee of Trigeminal Software, Inc. (TSI) developed a Form/Report to Data Access Page Wizard that overcomes many Save As DAP limitations. For example, the TSI Wizard handles most subforms and subreports, which open in an inline frame (<IFRAME>), and generates working drop-down lists (see Figure 25.31). The TSI Wizard is an Access add-in library (FrmRpt2Dap.mde) that you can download from http://www.trigeminal.com/frmrpt2dap.asp. Installation instructions are at http://www.trigeminal.com/frmrpt2dap_readme.asp. Data25.mdb in the \Seua11\Chaptr25 folder of the accompanying CD-ROM includes the Orders and Orders Subform pages generated by the TSI Wizard. The pages have minor design modifications, and the VBScript in the Orders.htm page has been altered to enable opening the subform directly from the Orders Subform.htm file.

Figure 25.31. Trigeminal Software, Inc.'s Form/Report to Data Access Page Wizard populates combo boxes and displays subforms in an inline frame.

Most of Microsoft's development investment in the upgrade from Office 2002 to Office 2003 is devoted to XML-related features. Microsoft's promotion of the .NET Framework for XML Web services has shifted the company's development focus to XML file generation manipulation by Office System 2003 members and Visual Studio .NET projects. Data access pages rely on HTML, which has a very limited repertoire of native control objects compared to conventional Windows applications. The capability to save complex Access objects to pages is, to a major extent, constrained by HTML 4.0 limitations. "If your only tool is HTML, everything looks like a <TABLE>, <TEXTAREA>, or <SPAN>" oversimplifies the issue but remains a valid aphorism.

Browser users are accustomed to crude Web-based data-entry forms and less-than-lightning response times, but they do expect attractive, consistent page graphics. The appearance of your pages is likely to be more important to executive and management types than their content or performance. Web page form over function priorities of nonusers is one of the reasons why this chapter and the preceding two chapters emphasize design changes to make pages more attractive. If your employer has a organization-wide page layout with standard logos, colors, fonts, and other design attributes, make sure that your DAP conform.