About saving an object as a data access page

Microsoft Office Access 2003

Default view (current view) Outcome Datasheet view A page that has controls arranged as a datasheet Form view A page that has controls arranged as a datasheet PivotTable view A page that uses a Microsoft Office PivotTable Component PivotChart view A page that uses a Microsoft Office Chart Component

If you carry out the Save As command after making changes to the object's formatting, but before saving your changes, the current formatting— not the saved formatting— will be used to create the page.

ShowImplications of using the Save As command

Control support    You will notice the following differences after saving a form or report as a data access page:

  • Bound object frames, unbound object frames, toggle buttons, and tab controls are not supported in data access pages. If the original object includes any of these controls, Microsoft Access will ignore them while creating the page.
  • Diagonal lines are not supported in data access pages, so diagonal lines in a form or report will appear as horizontal lines on a data access page.
  • Value lists as row sources are not supported in data access pages. Such controls will be left unbound on a page.
  • Data access pages don't support displaying multiple columns in list boxes and combo boxes, so you will see only the first visible column of the original control on a page.

Subforms and subreports    Subforms and subreports on a form or report are not converted when you carry out the Save As command. However, you can open the page in Design view and create additional group levels to make the page appear similar to the original object.

Control naming    Controls on forms and reports need not have unique names, but names of controls on a page must be unique. While creating the page, Access will change control names that are not unique.

Controls in the header and footer sections    Controls in the Form, Report, or page header sections will be placed as unbound controls in the caption section of the outermost group level. Controls in the Form, Report, or page footer sections will be placed as unbound controls in the navigation section of the outermost group level.

Code    Code in a form or report that cannot run from a data access page is imported into the page as a comment block at the end of the document.

Pictures    Pictures in a form or report are converted to bitmaps and placed in a folder named "Images".

Group level properties    By default, the AllowAdditions, AllowDeletions, and AllowEdits properties of all group levels in a data access page created from a report are set to False. However, you can open the page in Design view and change the property settings.

Expressions Expressions that refer to form or subform properties are ignored.

Security Note Data access pages aren't actually stored in the Access file; they are stored as HTML files either in the local file system, in a folder on a network share, or on an HTTP server. For this reason, Microsoft Access has no control over the security of data access page files. To help protect the data access page, you must employ security measures for its link and HTML file by using the file system security of the computer where you have stored these files. To help protect the data accessed by the page, you must either employ security measures for the database that the page is connected to or configure Microsoft Internet Explorer security settings to prevent unauthorized access.