| s-301
| This could break your application and require rewriting your application. |
| s-302
| In Access 2000, you can only programmatically change the ANSI SQL query mode and any queries created under ANSI-92 mode were hidden in the Database window. |
| s-303
| In Access 2002, you or a user can change ANSI SQL query mode through the user interface and ANSI-92 queries are no longer hidden in the Database window, so you should prevent accidental or intentional changes to the ANSI SQL query mode of your application by protecting your code and preventing the changing of the query mode through the application's user interface. |
| s-304
| Using ambiguous aliases and column names. |
| s-305
| To avoid confusion, ensure that aliases and column names are always unique in an SQL statement. |
| s-306
| About how Access searches for reference libraries |
| s-307
| The Visual Basic project of a Microsoft Access file contains references to object libraries, and it can also contain references to other files, including other Access files. |
| s-308
| The locations of referenced files are specified in the References dialog box that is available from the References command on the Tools menu in the Visual Basic Editor. |
| s-309
| When you open an Access file, if Access doesn't find a referenced file in the specified location, it searches for the reference as follows. |
| s-310
| First, Access searches for a RefLibPaths key in the following location in the Microsoft Windows Registry: |
| s-311
| If the key exists, Access checks for the existence of a value name that matches the name of the referenced file. |
| s-312
| If it finds a matching value name, Access loads the reference from the path specified in the corresponding value data. |
| s-313
| If Access doesn't find a RefLibPaths key, it searches for the referenced file in the locations listed below in the following order: |
| s-314
| Application folder containing the application (the folder where Msaccess.exe is located). |
| s-315
| Current folder. |
| s-316
| System folders (the System and System32 folders located in the Windows or WINNT folder). |
| s-317
| PATH environment variable. |
| s-318
| For more information about environment variables, see Windows Help. |
| s-319
| The folder that contains the Access file, and any subfolders located in that folder. |
| s-320
| If Access still can't find the reference after performing this search, you must fix the reference manually. |
| s-321
| About saving an object as a data access page |
| s-322
| You can also save tables, views, stored procedures, functions, and forms in a Microsoft Access project as a data access page. |
| s-323
| Saving an object as a data access page enables you to quickly convert an object into a page, and allows users of your application to review, enter, and analyze data over the Internet or an intranet. |
| s-324
| For example, if you have a sales report that you want to make available over the Web, instead of creating a data access page and customizing it to look like the sales report, you can save the report as a data access page. |
| s-325
| Using the Save As command on the File menu will save a data access page that is similar in appearance and functionality to the original report. |
| s-326
| If you want to make changes to the design of the resulting page, you can open the page in Design view and make any changes you want. |
| s-327
| The default view – the view in which the object is open when you carry out the Save As command – determines the design of the data access page. |
| s-328
| The following table lists the outcome of each view. |
| s-329
| Default view (current view) |
| s-330
| Outcome |
| s-331
| Datasheet view |
| s-332
| A page that has controls arranged as a datasheet |
| s-333
| Form view |
| s-334
| PivotTable view |
| s-335
| A page that uses a Microsoft Office PivotTable Component |
| s-336
| PivotChart view |
| s-337
| A page that uses a Microsoft Office Chart Component |
| s-338
| 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. |
| s-339
| Implications of using the Save As command |
| s-340
| Control support |
| s-341
| Such controls will be left unbound on a page. |
| s-342
| Subforms and subreports |
| s-343
| Subforms and subreports on a form or report are not converted when you carry out the Save As command. |
| s-344
| However, you can open the page in Design view and create additional group levels to make the page appear similar to the original object. |
| s-345
| Control naming |
| s-346
| Controls on forms and reports need not have unique names, but names of controls on a page must be unique. |
| s-347
| While creating the page, Access will change control names that are not unique. |
| s-348
| Controls in the header and footer sections |
| s-349
| Controls in the Form, Report, or page header sections will be placed as unbound controls in the caption section of the outermost group level. |
| s-350
| Controls in the Form, Report, or page footer sections will be placed as unbound controls in the navigation section of the outermost group level. |
| s-351
| Code in a form or report that can not run from a data access page is imported into the page as a comment block at the end of the document. |
| s-352
| Pictures in a form or report are converted to bitmaps and placed in a folder named 'Images '. |
| s-353
| Group level properties |
| s-354
| 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. |
| s-355
| However, you can open the page in Design view and change the property settings. |
| s-356
| Expressions that refer to form or subform properties are ignored. |
| s-357
| About sorting data in PivotTable or PivotChart view |