Chapter 11 - Upgrading from Previous Versions of MS Access

Article
02/20/2014

Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

This chapter tells you what to expect when you or your workgroup upgrades to Microsoft Access 97 from a previous version of Access. If you plan a gradual upgrade, users of different versions of Access may need to share databases. This chapter describes Access 97 features that are not supported in previous versions, which may require you to modify existing macros and application code.

Note Access runs on Windows 95 and Windows NT Workstation version 3.51 or later only.

See Also

For a summary of new and improved features in Access 97, see Chapter 2, "What's New in Microsoft Office."
For information about installing Access or other Microsoft Office applications, see Chapter 4, "Installing Microsoft Office."
For information about switching to Access from other database applications, see Chapter 17, "Switching to Microsoft Access."

Overview

The primary questions most Access 97 upgraders have are:

What happens to my old Access databases when I convert them to Access 97 format?
Can I share Access 97 databases with users of previous versions of Access?
Do my old macros still work in Access 97?
Does my old application code still work in Access 97?

If you are upgrading from any of the following versions of Access, this chapter answers these questions for you:

Access 95
Access version 2.0
Access version 1.x

Converting Databases

When you convert a database from a previous version of Access to Access 97, you can use all of the new features available in Access 97. After a database is converted, it cannot be opened in previous versions of Access, nor can it be converted back to an earlier format. You can, however, export tables from an Access 97 database to existing database in a previous version. Before you convert a database to Access 97 format, make sure that users who need to use the database have Windows 95 or Windows NT Workstation 3.51 or later and Access 97 installed on their computers.

Note If all the users in your workgroup have converted to Access 97, or if only Access 97 users work with the database, you can convert an Access 1.x, 2.0, or 95 database to Access 97. If users of previous versions of Access use the database, however, do not convert it. For more information about sharing databases across multiple versions, see "Sharing Databases with Microsoft Access 1.x, 2.0, or 95" later in this chapter.

If your database contains Access Basic or Microsoft Visual Basic for Applications code, you must fully compile your database before you convert it. Depending on the version of Access you are converting from, open a module in Access and on the Run menu, click the command shown in the following table.

If you are running this version of Access	Click this command on the Run menu
1.x	Compile All
2.0	Compile Loaded Modules
95	Compile All Modules

Important Before you convert the database, make a backup copy. If you are converting a database with linked (attached) tables, make sure these tables are in the folder referred to by the database you are converting. Finally, close the database before you convert it; if the database is located on a server or in a shared folder, make sure no other user has it open.

To convert a database

Start Access 97, and in the Startup dialog box, click Cancel.
On the Tools menu, point to Database Utilities, and then click Convert Database.
In the Database to Convert From dialog box, select the database you want to convert, and then click Convert.
In the Convert Database Into dialog box, type a new name (without the MDB extension) for the Access 97 database file, or select a different location if you want to keep the same name, and then click Save.

If you are converting a secured database, you must take additional steps. For more information, see "Converting a Database Secured with a Database Password" and "Converting a Database Secured with User-level Security" later in this section.

Why won't my database convert?

An Access 97 table can contain up to 32 indexes. Very complex tables that are a part of many relationships may exceed the index limit, so you cannot convert the database that contains these tables. Access 97 creates indexes on both sides of relationships between tables. If your database does not convert, open it in the version it was created with, delete some relationships, and then try converting the database again.

Under some circumstances, when a database from a previous version of Access has a large number of database objects, Access 97 may not be able to complete the conversion process. You may be able to resolve this problem by creating a new, blank database in Access 97, and then importing the objects from the older version database in groups until all of the objects have been imported.

Additionally, Visual Basic has a limit of 1,082 modules per database. Forms and reports each contain one module. If you receive an "Out of Memory" message when converting a large database, reduce the number of objects in your database or consider dividing your application into multiple databases. If you have modules with a large amount of code, consider using library databases to store the code. For more information about library databases, see Access online Help.

Converting Unbound Object Frame Controls to Image Controls

When you convert a database, you have the option to convert unbound object frame controls in forms and reports to image controls. This speeds up the opening of forms and reports, although the object displayed in the image control cannot be edited by double-clicking the control.

To convert unbound object frame controls to image controls when you convert a database

On the Database Utilities menu, click Convert Databases.
In the Database to Convert From dialog box, select the Convert OLE check box.

You can also convert an unbound object frame to an image control after converting the database.

To convert unbound object frame controls to image controls after you convert a database

On the Tools menu, point to Analyze, and then click Performance to starts the Performance Analyzer.

– or –

Open the form or report in Design view, right-click the control, point to Change To, and then click Image.

Converting a Database Secured with a Database Password

If a database has been secured by using a database password in Access 95, you must supply the password before you can convert the database. If this is the only form of security used with the database, then it is the only requirement to convert the database.

Converting a Database Secured with User-level Security

The workgroup information file is a database that stores the user names, passwords, and group accounts for a workgroup. In Access 1.x and 2.0, this file is called a workgroup or system database. Users of Access 97 can use workgroup information files and secure databases from previous versions of Access. However, users of a previous version of Access cannot use workgroup information files or databases in Access 97 format.

If a member of your workgroup who is not upgrading to Access 97 shares databases secured with user-level security, then have all Access 97 users in the workgroup join the workgroup information file that was created in the older version. Do not convert any databases shared by all users of the workgroup. For information about how you can share databases across versions, see "Sharing Databases with Microsoft Access 1.x, 2.0, or 95" later in this chapter.

If all members of a secure workgroup defined in a previous version of Access are upgrading to Access 97, convert all databases used by that workgroup. To convert a database that has been secured in a previous version of Access with user-level security, you must do the following:

Join the workgroup information file that defines the user accounts used to gain access to the database or that was in use when the database was created.

For the conversion, log on as a member of a user group, such as Admins, with the following permissions:
- Open/Run and Open Exclusive permissions for the database
- Modify Design or Administer permissions for all tables in the database, or ownership of all tables in the database
- Read Design permission for all of the objects in the database

If you are upgrading from Access 1.x or 2.0, after you convert a database secured with user-level security, recreate the workgroup information file used with it. For more information, see "Recreating Microsoft Access 1.x and 2.0 Workgroup Information Files" later in this section.

Note If you are upgrading from Access 95, use the workgroup information file from Access 95, but compact it with Access 97 before using it. For information about compacting a workgroup information file, see Access online Help.

Joining the Original Workgroup Information File

The Office Setup program creates a new workgroup information file named System.mdw in the System folder (Windows 95) or the System32 folder (Windows NT Workstation 3.51 or later), and specifies that file as your current workgroup information file. If, before upgrading, you are a member of a secure workgroup, you must join your original workgroup information file after upgrading to open or convert secured databases.

To join a workgroup information file from a previous version of Access

In the System folder (Windows 95) or System32 folder (Windows NT Workstation 3.51 or later), double-click Wrkgadm.exe.
In the Workgroup Administrator dialog box, click Join.
In the Database box, enter the name of the workgroup information file you want to join.

In Windows 95 and Windows NT Workstation version 4.0, you can also click Run on the Windows Start menu, and type msaccess.exe /wrkgrp file name to join the workgroup information file.

Note You can automatically join a workgroup information file every time you start Access 97, using the /wrkgrp command-line option. For information about using command-line options, see Access online Help.

For more information about the user-level security model, see Chapter 29, "Workgroup Features in Microsoft Access."

Recreating Microsoft Access 1.x and 2.0 Workgroup Information Files

If all members of a secure workgroup from Access 1.x or 2.0 are upgrading to Access 97, recreate their workgroup information file in Access 97 format before they need to use it. Although Access 97 can use workgroup information files from a previous version, additional memory is required to do so. Additionally, when users upgrade to the new workgroup information file, they can all view their group memberships.

The following procedures show how to recreate a workgroup information file in Access 97 format. To complete this task, you must know the exact, case-sensitive user names, group names, and personal IDs used to create the accounts in the workgroup. You must also know the exact, case-sensitive name, company name, and workgroup ID used to create the original file.

Note If you do not have the information to recreate the workgroup information file, continue to use the previous version; however, only members of the Admins group can view group memberships.

To create the new workgroup information file in Access 97

In Windows Explorer (Windows 95 or Windows NT Workstation 4.0) or File Manager (Windows NT Workstation 3.51), double-click Wrkgadm.exe in the System folder (for Windows 95) or the System32 folder (for Windows NT Workstation 3.51 or later).
In the Workgroup Administrator dialog box, click Create.
In the Workgroup Owner Information dialog box, enter the exact, case-sensitive name, company name, and workgroup ID used to create the original file.

If you fail to enter the exact entries used to create the original file, an invalid Admins group is created.

After you have created a new workgroup information file with the original Admins group, you must recreate any user and group accounts.

To recreate the user and group accounts for a workgroup information file

On the Access Tools menu, point to Security, and then click User and Group Accounts.
To recreate any group accounts, click the Groups tab, and then click New; type the exact, case-sensitive group names and personal IDs and click OK.
To recreate previous user accounts, click the Users tab, and then click New; type the exact, case-sensitive user names and personal IDs and click OK.
In the User and Group Accounts dialog box, click Add to add users to the appropriate groups, and click Remove to remove the Admin user from the Admins group.
Click the Change Logon Password tab, and define a password for the Admin user.
Close the User and Group Accounts dialog box and exit Access; then restart and log on as a member of the Admins group.
On the Tools menu, point to Security, and then click User and Group Accounts to define a password for this account.

When you finish these procedures, the user and group accounts are recreated. The only passwords defined so far are the ones you defined in Steps 5 and 7. You may want to define passwords for other accounts, or users can log on and define their own passwords. As long as you entered the exact, case-sensitive name, company name, and workgroup ID when creating the new file, and the exact, case-sensitive names and personal IDs when setting up the new accounts, all user and group accounts have the same permissions as the accounts in the workgroup information file from the previous version of Access.

Note In Access 95 and 97, new workgroup information files have an .mdw extension by default. In previous versions, workgroup information files have an .mda extension. The .mdw extension uniquely identifies workgroup information files and prevents them from appearing in dialog boxes for library database (MDA) files. However, you can use the Workgroup Administrator to join or create workgroup information files with .mda extensions.

Converting a Replicated Database

You cannot convert a replicated database from Access directly. Instead, synchronize it with a converted Design Master. A Design Master is the first replica in a replica set to which system tables, system fields, and replication properties have been added. You can make changes to the database structure through the Design Master only. In a replica set, any replica can be the Design Master, but only one at a time.

For the conversion to work, all members of the replica set must be accessed from computers with Access 97 installed. Also, the Design Master must have been opened in Access 95 at least once after it was created before you can convert it. If the Design Master was not opened after it is created, and you try to convert it in Access 97, a message displays. In this case, you must open the Design Master in Access 95 before you can continue. If you want to use a single computer for the conversion, it must be running both Access 95 and 97. For information about running these two versions of Access on the same computer, see "Running Multiple Versions of Microsoft Access on a Single Computer" in Chapter 22, "Supporting Multiple Versions of Microsoft Office."

Note You can allow an Access 95 replica to run in Access 97 without conversion through a process called enabling. However, if you open an enabled Access 95 replica in Access 97 and the replica has not yet been synchronized, Access warns you that there is a synchronization pending that cannot occur until the replica is opened and synchronized in Access 95. For more information about enabling databases, see "Enabling a Database" later in this chapter.

It is best to take a conservative approach when converting a replica set. The following procedure allows you to test a temporary second replica set before committing your original set to the conversion.

Caution It is important that you do not synchronize the test Design Master and replicas with members of your working replica set. Otherwise, unintended changes to the data or structure of your working replica set may occur.

To convert a replica set

Make a copy of the current Design Master (created in Access 95), and put the copy on a different computer or isolate it completely from any other members of the replica set.
In Access 95, make the isolated copy the new Design Master by pointing to Replication on the Tools menu, and then clicking Recover Design Master.
Create some replicas based on the new Design Master.
In Access 97, point to Database Utilities on the Tools menu, and then click Convert Database to convert the new Design Master to an Access 97 database.
On the Tools menu, point to Replication, and then click Synchronize Now to synchronize the new Design Master with the newly created replicas.
Run any tests you would like to try.

If you want to change some objects, you can either make the changes again in the original Design Master after it is converted, or keep the copy and import the changed objects from it.
Once you are satisfied that the copy works, delete the new Design Master and all of its replicas. Make sure that all users who open the Design Master and replica databases have installed Access 97.
Convert the original Design Master to Access 97, and then synchronize it with the original replicas.

Important You cannot open synchronized replicas again in Access 95. Once you open the replicas in Access 97, they are irrevocably converted.

Working with MS Access 1.x and 2.0 Databases with Attached ODBC Tables

Access 97 can convert or enable Access 1.x and 2.0 databases that have attached (linked) tables. However, Access 97 cannot open linked tables that refer to Open Database Connectivity (ODBC) sources which use a 16-bit ODBC driver manager and driver. For example, if an Access 1.x or 2.0 database refers to an ODBC data source, such as an SQL Server table, the linked table's data source name (DSN) uses the 16-bit version of the ODBC driver manager (Odbc.dll) and the corresponding driver, such as the 16-bit Microsoft SQL Server ODBC driver (Sqlsrvr.dll).

Access 97 can open only linked ODBC data sources that use the 32-bit versions of the ODBC driver manager (Odbc32.dll) and the appropriate ODBC driver, such as the 32-bit version of Microsoft SQL Server ODBC driver (Sqlsrv32.dll).

When Access 97 converts or enables an Access 1.x or 2.0 database with linked ODBC tables, it cannot automatically create new DSNs that use the 32-bit versions of the ODBC driver manager and ODBC driver. When you convert or enable such a database, if you try to open the table or a form that uses the table for its record source, Access displays the message "ODBC connection to datasourcename failed." When you close this message, Access 97 displays another message indicating that it cannot open the table or form.

To correct this problem, you must first make sure that the 32-bit versions of the ODBC driver manager and the appropriate driver are installed, and then create a new, identically named DSN for each ODBC data source that is linked to the original database.

ODBC drivers are not installed when you choose a Typical installation during Setup. To install the 32-bit version of the Microsoft SQL Server ODBC Driver, rerun the Setup and click Add/Remove. Under the Microsoft Access option, select Data Access, select Database Drivers, and then select the Microsoft SQL Server Driver option.

Note If the original database does not use the Microsoft SQL Server ODBC Driver, you must contact the vendor of the driver to obtain a 32-bit version of the driver.

After the appropriate driver is installed, create a new, identically named DSN for each ODBC data source that is linked to the original database.

Note In the following procedure, if the 32bit ODBC icon is not available in Control Panel, rerun Setup and install the Microsoft SQL Server ODBC Driver as described earlier. Installing the Microsoft SQL Server ODBC Driver also installs the 32-bit version of the ODBC driver manager and other ODBC support files.

To create a new, identically named 32-bit DSN

In Control Panel, double-click the 32bit ODBC icon.
In the ODBC Data Source Administrator dialog box, click the appropriate DSN tab.

For information about using the User DSN, System DSN, and File DSN tabs, click Help.
Click Add.
In the Create New Data Source panel, select the appropriate driver, and then click Finish.
In the dialog box, enter values identical to the original DSN.

For example, for Microsoft SQL Server you must define the Data Source Name and Server. You may also need to click Options and define additional values, such as the Database Name.

If you do not know the original name of the DSN, open the original database in the version of Access in which it was created, open the linked table in Design view, and then display the Table Properties sheet. The Description property contains the definition for the ODBC connection string. The parameter following DSN= in the connection string is the name of the DSN. To view the rest of the DSN definition, open Control Panel and double-click the ODBC icon (not the 32bit ODBC icon). In the Data Source (Driver) box, click the name of the DSN, and then click Setup to view the definition of the DSN.

For more information about enabling a database, see "Enabling a Database" later in this chapter.

Upgrading from MS Access 95

This section describes the differences between Access 95 and Access 97. Access 97 is a major upgrade from previous versions of the application. For more information about the features and benefits of this upgrade, see Chapter 2, "What's New in Microsoft Office."

What happens to my old Access databases when I convert them to Access 97 format? You can open databases created in Access 95 directly in Access 97, even if you do not convert the database through a process called enabling. Once you convert an Access 95 database to Access 97 format, you cannot open it in Access 95, and it cannot be converted back to Access 95 format.

Can I share Access 97 databases with users of previous versions of Access? If your workgroup is using a combination of Access 97 and 95, users can share data and databases. However, not all Access 97 features are supported in previous versions.

Do my old macros still work in Access 97? In most cases, macros created in Access 95 run in Access 97. If you convert or enable an Access 95 database containing macros in Access 97, the macros run in Access 97.

Does my old Visual Basic application code still work in Access 97? In most cases, Visual Basic code created in Access 95 runs in Access 97. If you convert an Access 95 database to Access 97, the Visual Basic code is converted to equivalent Visual Basic code that runs in Access 97. If you enable an Access 95 database in Access 97, a copy of the Visual Basic code is converted to equivalent Visual Basic code that runs in Access 97; your original code is not altered.

The following sections summarize the Access 95 commands that have changed location or functionality in Access 97, as well as commands that are new in Access 97.

The following table describes changed commands on the File menu.

This Access 95 command	Changes to this in Access 97
Toolbars (when no database is open)	Moved to the View menu.
Unhide (when no database is open)	Moved to the Window menu.

The following table lists new commands that have been added to the File menu.

This Access 97 command	Allows you to
Save As HTML	Save tables, queries, forms, and reports so that they can be read by a World Wide Web browser. For more information about Access 97 Internet features, see Chapter 25, "Web Support in Microsoft Office Applications."

The following table lists new commands that have been added to the Edit menu.

This Access 97 command	Allows you to
Paste As Hyperlink	Paste and format the Clipboard contents as a hyperlink. You must then edit the hyperlink using the Hyperlink command (Insert menu) to specify a file or URL to which the selected item is to be linked. For more information about Access 97 Internet features, see Chapter 25, "Web Support in Microsoft Office Applications."
List Properties/Methods	Display all properties and methods for the statement containing the insertion point in the Module window.
List Constants	Display all constants for the statement containing the insertion point in the Module window.
Quick Info	Display syntax information for the variable, constant, or procedure at the insertion point in the Module window.
Parameter Info	Display all parameters for the statement containing the insertion point in the Module window.
Complete Word	Complete the typing of a property, method, or constant word fragment in the Module window. Use to display all possible choices if a word fragment is not unique.
Bookmarks submenu commands	Add, delete, and move between bookmarks in the Module window. Use bookmarks for designating important lines of code in long modules.

The following table describes changed commands on the View menu.

This Access 95 command	Changes to this in Access 97
Toolbars	Replaced by Toolbars submenu.
1, 2, 4, 8, 12 (Pages submenu in Print Preview)	Renamed One Page, Two Pages, Four Pages, Eight Pages, Twelve Pages.
Procedure Definition (in the Module window)	Renamed Definition.

The following table lists new commands that have been added to the View menu.

This Access 97 command	Allows you to
Toolbars submenu commands	Display and hide toolbars. Includes the new Customize command for creating and customizing toolbars and menu bars.

The following table describes changed commands on the Insert menu.

This Access 95 command	Changes to this in Access 97
Custom Control (in form and report Design view)	Renamed ActiveX Control.
Field (in table Design view)	Renamed Rows.
Record (in query Datasheet view)	Renamed New Record.
Row (in query and macro Design view)	Renamed Rows.
Column (in query Design view)	Renamed Columns.

The following table lists new commands that have been added to the Insert menu.

This Access 97 command	Allows you to
Hyperlink	Insert a Web-style hyperlink to another Office document. In Datasheet and Form views, a hyperlink column must be selected. For more information about hyperlinks, see Chapter 24, "Integrating Microsoft Office with Your Intranet."
Tab Control Page (in form Design view)	Insert a new page to the right of existing pages on a tab control and place it first in the page order sequence.
This Access 97 command	Allows you to
Hyperlink Column (in table Datasheet view)	Create a new column (field) and set its data type to Hyperlink. Use hyperlink columns to store and go to hyperlink addresses.
Class Module (in the Module window)	Insert a class module that is not associated with a form or report into the current database and display its Declarations section.

The following table describes changed commands on the Run menu.

This Access 95 command	Changes to this in Access 97
Continue	Renamed Go/Continue.
Step Into	Moved to the Debug menu.
Step Over	Moved to the Debug menu.
Step To Cursor	Renamed Run To Cursor and moved to the Debug menu.
Toggle Breakpoint	Moved to the Debug menu.
Clear All Breakpoints	Moved to the Debug menu.
Set Next Statement	Moved to the Debug menu.
Show Next Statement	Moved to the Debug menu.
Compile Loaded Modules	Moved to the Debug menu.
Compile All Modules	Moved to the Debug menu.

The Debug menu is new in Access 97. It contains many commands that were on the Run and Tools menus in Access 95. In addition, the following table lists new commands that have been added to the Debug menu.

This Access 97 command	Allows you to
Step Out	Run all lines of code and nested procedures in Break mode, beginning with the current executable statement, and then return execution to the preceding procedure in the call tree. Use to avoid stepping through each line of code that calls multiple nested procedures.
Compile and Save All Modules	Compile and save all modules in the database in a single operation.

The following table describes changed commands on the Tools menu.

This Access 95 command	Changes to this in Access 97
Custom Controls	Renamed ActiveX Controls.
Merge It (Office Links submenu)	Renamed Merge It With MS Word.
Documentor (Analyze submenu)	Renamed Documenter.
Calls	Renamed Call Stack and moved to the View menu.
Add Watch	Moved to the Debug menu.
Edit Watch	Moved to the Debug menu.
Instant Watch	Renamed Quick Watch and moved to the Debug menu.
Macro	Renamed Run Macro and moved to the Macro submenu (in the Database window).

The following table lists new commands that have been added to the Tools menu.

This Access 97 command	Allows you to
Make MDE File (Database Utilities submenu)	Copy a database to an MDE database format. Use to secure Visual Basic source code by removing it, and prevent users from modifying forms, reports, and modules. For more information about MDE databases, see Chapter 29, "Workgroup Features in Microsoft Access."
Macro submenu commands (in the Database window)	Create, run, and manage macros; convert macros to Visual Basic, and create a new Access 97-style menu bar, toolbar, or shortcut menu from a macro.

The following table describes changed commands on the Window menu.

This Access 95 command	Changes to this in Access 97
Split Window (in module Design view)	Renamed Split.

The following table describes changed commands on the Help menu.

This Access 95 command	Changes to this in Access 97
Microsoft Access Help Topics	Renamed Microsoft Access Help. This command displays the Office Assistant, through which you view Help.
Answer Wizard	Removed. Use the Assistant to gain access to the Answer Wizard feature.

The following table lists new commands that have been added to the Help menu.

This Access 97 command	Allows you to
What's This?	Click any area of the screen (such as a toolbar or menu command) to see a brief explanation in a ScreenTip.
Microsoft on the Web submenu commands	Connect to the Microsoft home page on the Web (requires Internet access).

File Format Changes

The format of Access tables is the same in Access 95 and 97. This means that you can:

Import an Access 97 table into an Access 95 database.
Link an Access 97 table to an Access 95 database.
Export an Access 97 table to an Access 95 database.
Cut, copy, and paste from an Access 97 table to an Access 95 table.

Note When you export or import Microsoft 97 tables into Access 95, fields with the Hyperlink data type are converted to fields with the Memo data type and their hyperlink functionality is lost.

The format of database objects other than tables is different in Access 97. You cannot import, link, export, cut, copy, or paste these Access 97 database objects to Access 95.

Using the Same Table in Microsoft Access 95 and 97

The fact that tables share the same format in Access 95 and 97 is useful if you have front-end and back-end databases that must be shared by users of both versions. Users of both Access 97 and Access 95 can open tables in the back-end database that are in either version. For more information about front-end and back-end databases, see "Creating a Front-end Database Linked to Table Data in a Previous Version Back-end Database" later in this chapter.

If your workgroup is upgrading gradually to Access 97, Access 97 users may have to share databases with Access 95 users. Access supports several strategies for sharing databases between different versions. For more information about changes in file format and strategies for sharing databases, see "Sharing Databases with Microsoft Access 1.x, 2.0, or 95" later in this chapter.

Template Changes

The Access 97 Report Wizard, Form Wizard, and the AutoFormat command (Format menu) provide formatting features that are similar to Microsoft Word and Microsoft Excel AutoFormats and templates. The Access 97 Database Wizard is similar to a template in that it provides predefined choices that are used to create new databases. Access 97 allows users to select from a number of other add-ins and wizards, which also function like templates by providing predefined choices when creating a new table, query, and some properties and controls.

Previous versions of Access allow users to customize wizards; however, these customized wizards cannot be converted to Access 97 format. Any customization of Access 97 wizards must be performed by using the commands available in the Access 97 wizards.

To create a form or report without using a wizard, click Form or Report (Insert menu), and then click Design New. The template used when you create forms or reports this way is set by using the Forms/Reports tab in the Options dialog box (Tools menu). In order to use a template from previous versions of Access, you must convert it to Access 97 format.

Macro Changes

In most cases, macros defined in Access 95 run in Access 97 for both converted and enabled databases. However, changes to menus, commands, and other user interface elements may mean that some of your macros must be rewritten, particularly those that include the SendKeys or the DoMenuItem action.

SendKeys Action

A macro from a previous version of Access that uses the SendKeys action does not function properly if the arguments refer to menu commands or dialog box options that have changed. For alternatives to using the SendKeys action, see "Using the SendKeys Statement or Action" later in this chapter.

DoMenuItem Action

In Access 97, the RunCommand action replaces the DoMenuItem action, which is included in Access 97 only for compatibility with previous versions. When you open and save a macro from a previous version of Access that contains a DoMenuItem action, the action and its arguments are automatically converted to the equivalent RunCommand action. The DoMenuItem action no longer appears in the list of actions in the Macro window in Access 97.

When you convert a database from a previous version of Access, some commands may no longer be available. The command may have been renamed, moved to a different menu, or removed entirely. The DoMenuItem actions for such commands are converted to RunCommand actions with a blank Command argument. You must edit the macro and enter a valid RunCommand action, or delete the action.

When you enable a database from a previous version of Access, the DoMenuItem action continues to work properly. DoMenuItem methods used in Visual Basic procedures are unchanged.

Visual Basic Code Changes

Access 97 supports some new Visual Basic keywords, so you can no longer use these keywords as identifiers. These keywords are:

AddressOf
Assert
Decimal
DefDec
Enum
Event
Friend
Implements
RaiseEvent
WithEvents

For information about how these new keywords can affect converted or enabled databases, see "Identifiers with the Same Names as Visual Basic Keywords" later in this chapter.

New Toolbars, Menus, and Shortcut Menus

Access 97 supports a new style of toolbars, menus, and shortcut menus. When you convert a database from a previous version of Access to Access 97, any custom toolbars are automatically converted to the new style.

Custom menus and shortcut menus created in a previous version of Access are handled differently. Previous versions of Access use the Menu Builder to create custom menus and shortcut menus. The Menu Builder generates a macro group containing macros that use the AddMenu and DoMenuItem actions. In previous versions of Access, you can also create custom menus and shortcut menus manually (without the Menu Builder), using these macro actions. Custom menu and shortcut menu macros created using either method still run Access 97, but they are not converted to the new style, nor are they available from the new Customize dialog box (View menu, Toolbars submenu).

To save a menu or shortcut menu from a previous version of Access in Access 97 format, select the macro group used to create the menu or shortcut menu in the Database window, and then click Create Menu from Macro or Create Shortcut Menu from Macro (Tools menu, Macro submenu). Unlike new custom menus or shortcut menus created with the Customize dialog box, these menus and shortcut menus depend on the macro group from the previous version of Access. If you delete this macro group or any macros it refers to, the menu or shortcut menu no longer works. Alternatively, you can use the Customize dialog box (View menu, Toolbars submenu) to recreate custom toolbars, menu bars, and shortcut menus.

Upgrading from MS Access 2.0

This section describes the changes between Access 2.0 and Access 97. Access 97 is a major upgrade from previous versions of the application. For more information about the features and benefits of this upgrade, see Chapter 2, "What's New in Microsoft Office."

What happens to my old Access databases when I convert them to Access 97 format? You can open databases created in Access 2.0 directly in Access 97, even if you do not convert the database. To do so, you must perform a process called enabling. Once you convert an Access 2.0 database to Access 97 format, you cannot open it in Access 2.0, and it cannot be converted back to Access 2.0 format.

Can I share Access 97 databases with users of previous versions of Access? If your workgroup is using a combination of Access 97 and 2.0, users can share data and databases. However, not all Access 97 features are supported in previous versions.

Do my old macros still work in Access 97? In most cases, macros created in Access 2.0 run in Access 97. If you convert or enable an Access 2.0 database containing macros in Access 97, the macros run in Access 97.

Does my old Access Basic application code still work in Access 97? In most cases, Access Basic application code created in Access 2.0 runs in Access 97. If you convert an Access 2.0 database to Access 97, the Access Basic code is converted to equivalent Visual Basic code. If you enable an Access 2.0 database in Access 97, a copy of the Access Basic code is converted to equivalent Visual Basic code; your original code is not altered.

The following sections summarize the Access 2.0 commands that have changed location or functionality in Access 97, as well as commands that are new in Access 97.

The following table describes changed commands on the File menu.

This Access 2.0 command	Changes to this in Access 97
Compact Database (when no database is open)	Moved to Tools menu (Database Utilities submenu).
Convert Database (when no database is open)	Moved to Tools menu (Database Utilities submenu).
Encrypt/Decrypt Database (when no database is open)	Moved to Tools menu (Security submenu).
Repair Database (when no database is open)	Moved to Tools menu (Database Utilities submenu).
Toolbars (when no database is open)	Moved to View menu.
Unhide (when no database is open)	Moved to Window menu.
Run Macro (when no database is open)	Moved to Tools menu (Macro submenu).
Add-ins (when no database is open)	Moved to Tools menu and is available only when a database is open.
Close Database	Renamed Close.
New submenu commands	Moved to Insert menu.
Rename	Moved to Edit menu.
Output To and Export	Consolidated in Save As/Export.
Import	Moved to Get External Data submenu.
Attach Table	Renamed Link Tables (Get External Data submenu).
Imp/Exp Setup	Removed. Click the Advanced button in the Import Text Wizard or Export Text Wizard to work with Import/Export specifications.
Print Setup	Renamed Page Setup.
Print Definition	Replaced by Documenter (Tools menu, Analyze submenu).
Save Layout (in the Relationships window)	Renamed Save.
Save As and Output To (in table and query Design view)	Consolidated in Save As/Export.
Save Table (in table Datasheet view)	Renamed Save.
Save Query (in query Datasheet view)	Renamed Save.
Save Form (in Form view and form Datasheet view)	Renamed Save.
Save Query As (in query Datasheet view)	Renamed Save As/Export.
Save Form As (in Form view and form Datasheet view)	Renamed Save As/Export.
Save Record (in Form and Datasheet view)	Moved to Records menu.
Save As Report (in form Design view)	Removed. Right-click a form in the Database window to save a form as a report.
Sample Preview (in report Design view)	Renamed Layout Preview (View menu).
Load Text (in the Module window)	Replaced by Import (Get External Data submenu).
Save Text (in the Module window)	Renamed Save As Text.

The following table lists new commands that have been added to the File menu.

This Access 97 command	Allows you to
Save As HTML	Save tables, queries, forms, and reports so that they can be read by a World Wide Web browser. For more information about Access 97 Internet features, see Chapter 25, "Web Support in Microsoft Office Applications."

The following table describes changed commands on the Edit menu.

This Access 2.0 command	Changes to this in Access 97
Relationships	Moved to Tools menu.
Insert Row (in table and query Design view)	Renamed Rows (Insert menu).
Set Primary Key (in table Design view)	Renamed Primary Key.
Undo All (in query Design view)	Removed.
Insert Column (in query Design view)	Renamed Column (Insert menu).
Undo Current Field (in table, query, and form Datasheet view)	Renamed Undo Current Field/Record.
Insert Object (in table, query, and form Datasheet view)	Renamed Object (Insert menu).
Links (in table, query, and form Datasheet view)	Renamed OLE/DDE Links.
Tab Order (in form and report Design view)	Moved to View menu.
Find Previous (in the Module window)	Removed. Use Find to search backwards.
New Procedure (in the Module window)	Renamed Procedure (Insert menu).

The following table lists new commands that have been added to the Edit menu.

This Access 97 command	Allows you to
Create Shortcut	Create a shortcut for the selected object in the Database window so that you can quickly open it by clicking an icon.
Paste As Hyperlink	Paste and format the Clipboard contents as a hyperlink. Edit the hyperlink using the Hyperlink command (Insert menu) to specify a file or URL. For more information about hyperlinks, see Chapter 24, "Integrating Microsoft Office with Your Intranet."
Indent	Do the equivalent of pressing TAB in the Module window.
Outdent	Do the equivalent of pressing SHIFT+TAB in the Module window.

The following table describes changed commands on the View menu.

This Access 2.0 command	Changes to this in Access 97
Tables	Moved to Database Objects submenu.
Queries	Moved to Database Objects submenu.
Forms	Moved to Database Objects submenu.
Reports	Moved to Database Objects submenu.
Macros	Moved to Database Objects submenu.
Modules	Moved to Database Objects submenu.
Table Properties (in table Design view)	Renamed Properties.
Palette (in form and report Design view)	Removed. Use the Formatting toolbar to perform palette functions.
Control Wizards (in form and report Design view)	Functionality moved to the Control Wizards button (Toolbox toolbar).
Split Window (in the Module window)	Renamed Split(Window menu).
Procedures (in the Module window)	Replaced by Object Browser.
Next Procedure (in the Module window)	Removed.
Previous Procedure (in the Module window)	Removed.
Immediate Window (in the Module window)	Renamed Debug Window.
Calls (in the Module window)	Renamed Call Stack.
Toolbars	Moved to the Toolbars submenu.

The following table lists new commands that have been added to the View menu.

This Access 97 command	Allows you to
Pages submenu commands (in layout preview or print preview)	Display 1, 2, 4, 8, or 12 pages in progressively smaller thumbnail views.
Definition	Display the procedure code of the procedure name at the insertion point in the Module window. If the procedure is defined in a DLL, Access displays the Declare statement used to define the DLL entry point.
Customize (Toolbars submenu)	Display and hide toolbars, and create and customize toolbars and menu bars.

The Insert menu is new in Access 97. It contains many commands that were on other menus in Access 2.0. In addition, the following table lists new commands that have been added to the Insert menu.

This Access 97 command	Allows you to
ActiveX Control	Add an ActiveX control (formerly a custom control or OLE control) to a form or report. ActiveX controls are stored as separate files and must be entered in the Windows registry.
Hyperlink	Insert a Web-style hyperlink to another Office document. In Datasheet and Form views, a hyperlink column must be selected. For more information about hyperlinks, see Chapter 24, "Integrating Microsoft Office with Your Intranet."
Tab Control Page (in form Design view)	Insert a new page to the right of existing pages on a tab control and place it first in the page order sequence.
Hyperlink Column (in table Datasheet view)	Create a new column (field) and set its data type to Hyperlink. Use hyperlink columns to store and go to hyperlink addresses.
Class Module (in the Module window)	Insert a class module that is not associated with a form or report into the current database and display its Declarations section.
AutoForm	Automatically create a form for the table or query selected in the Database window.
AutoReport	Automatically create a report for the table or query selected in the Database window.

The Tools menu is new in Access 97. It contains many commands that were on other menus in Access 2.0. In addition, the following table lists new commands that have been added to the Tools menu.

This Access 97 command	Allows you to
Make MDE File (Database Utilities submenu)	Copy a database to an MDE database format. Use to secure Visual Basic source code by removing it, and prevent users from modifying forms, reports, and modules. For more information about MDE databases, see Chapter 29, "Workgroup Features in Microsoft Access."
Macro submenu commands (in the Database window)	Create, run, and manage macros; convert macros to Visual Basic, and create Access 97 style menu bars, toolbars, and shortcut menus from macros.

The following table describes changed commands on the Relationships menu.

This Access 2.0 command	Changes to this in Access 97
Add Table	Renamed Show Table.
Remove Table	Replaced by Hide Table.
Create Relationship	Removed.

The following table describes changed commands on the Query menu.

This Access 2.0 command	Changes to this in Access 97
Add Table	Renamed Show Table.
Join Table	Removed.

The following table describes changed commands on the Format menu.

This Access 2.0 command	Changes to this in Access 97
Gridlines (in Datasheet view)	Removed. Use the Cells command to format gridlines.
Apply Default (in form Design view)	Replaced by AutoFormat.
Change Default	Renamed Set Control Defaults.
Page Header/Footer	Moved to View menu.
Form Header/Footer	Moved to View menu.

The following table describes changed commands on the Records menu.

This Access 2.0 command	Changes to this in Access 97
Go To	Moved to Edit menu.
Quick Sort	Renamed Sort.
Edit Filter/Sort	Renamed Filter.
Allow Editing	Removed.

The Macro menu in module Design view has been renamed the Run menu.

The following table describes changed commands on the Run menu. (In Access 2.0, these commands appear on the Macro menu in module Design view.)

This Access 2.0 command	Changes to this in Access 97
Compile Loaded Modules	Renamed Compile All Modules (Debug menu).
Continue	Renamed Go/Continue.
Step Into	Moved to Debug menu.
Step Over	Moved to Debug menu.
Set Next Statement	Moved to Debug menu.
Show Next Statement	Moved to Debug menu.
Toggle Breakpoint	Moved to Debug menu.
Clear All Breakpoints	Moved to Debug menu.
Modify Command$	Removed.

The Debug menu is new Access 97. It contains many commands that were on the Run menu in Access 2.0. In addition, the following table lists new commands that have been added to the Debug menu.

This Access 97 command	Allows you to
Step Out	Run all lines of code and nested procedures in Break mode, beginning with the current executable statement, and then return execution to the preceding procedure in the call tree. Use to avoid stepping through each line of code that calls multiple nested procedures.
Compile and Save All Modules	Compile and save all modules in the database in a single operation.

The following table describes changed commands on the Window menu.

This Access 2.0 command	Allows you to
Tile	Replaced by Tile Horizontally and Tile Vertically.

The following table describes changed commands on the Help menu.

This Access 2.0 command	Allows you to
Contents	Renamed Contents and Index.
Search and Cue Cards	Removed. Use Microsoft Access Help to display the Office Assistant, through which you view Help.
Technical Support	Functionality moved to the Tech Support button in the About Microsoft Access dialog box.

The following table lists new commands that have been added to the Help menu.

This Access 97 command	Allows you to
Contents and Index	Display the Access Help.
What's This?	Click any area of the screen (such as a toolbar or menu command) to see a brief explanation in a ScreenTip.
Microsoft on the Web submenu commands	Connect to the Microsoft home page on the Web (requires Internet access).

File Format Changes

The format of Access 97 databases and the database objects within them is different from Access 2.0 databases and objects. You cannot import, link (attach), export, cut, copy, or paste from Access 97 database objects to Access 2.0. However, you can do the following:

Import Access 2.0 database objects into Access 97.
Link (attach) Access 2.0 tables in an Access 97 database.
Export an Access 97 table to an Access 2.0 database.

Note When you export tables to Access 2.0, fields with the Hyperlink data type are converted to fields with the Memo data type and hyperlink functionality is lost. Functionality of fields with the following property settings is lost:
- Lookup property settings
- AutoNumber data type with the FieldSize property set to ReplicationID
- AutoNumber data type with the NewValues property set to Random

If your workgroup is upgrading gradually to Access 97, Access 97 users may have to share databases with Access 2.0 users. Access supports several strategies for sharing databases between different versions. For more information about changes in file format and strategies for sharing databases, see "Sharing Databases with Microsoft Access 1.x, 2.0, or 95" later in this chapter.

Template Changes

The Access 97 Report Wizard, Form Wizard, and the AutoFormat command (Format menu) provide formatting features that are similar to Microsoft Word and Excel AutoFormats and templates. The Access 97 Database Wizard is similar to a template in that it provides predefined choices that are used to create new databases. Access 97 allows users to select from a number of other add-ins and wizards, which also function like templates by providing predefined choices when creating a new table, query, and some properties and controls.

Note Previous versions of Access allow users to customize wizards; however, these customized wizards cannot be converted to Access 97 format.

To create a form or report without using a wizard, click Form or Report (Insert menu), and then click Design New. The template used when you create forms or reports this way is set by clicking the Forms/Reports tab in the Options dialog box (Tools menu). In order to use a template from previous versions of Access, you must convert it to Access 97 format.

Macro Changes

In most cases, macros defined in Access 2.0 run in Access 97 for both converted and enabled databases. However, changes to menus, commands, and other user interface elements may mean that some of your macros must be rewritten, particularly those that include the SendKeys action. In addition, some macro actions work differently in Access 97 than in Access 1.x and 2.0. This section explains these differences.

Using the SendKeys Statement or Action

If you are converting an Access 1.x or 2.0 database to Access 97, changes in some dialog boxes and menus may require you to recode the SendKeys statement or SendKeys action. For example, the Add-ins submenu has been moved from the File menu to the Tools menu, and the previous Import and Attach commands on the File menu have moved to the Get External Data submenu. Because changes like this are likely to occur for each new version of Access, avoid using the SendKeys statement or action to carry out commands or fill in dialog boxes wherever possible.

If you must use the SendKeys statement or action, consider the following guidelines:

Before you use the SendKeys statement or action to carry out a menu command, check for an equivalent macro action or Visual Basic method.

Most commands that are commonly carried out by a menu command or option have an equivalent action or method. For example, you can now use the Dropdown method of a combo box rather than the code SendKeys "{F4}".
If a menu command does not have an equivalent action or method, use the RunCommand action rather than the SendKeys statement or action.
Avoid using the SendKeys statement or action to set options in the Options dialog box.

New versions of Access are likely to have new and changed options, so the code in your SendKeys statement or action could easily break. Instead, use the GetOption and SetOption methods.
When you use the SendKeys statement to carry out an action, consider referencing the built-in key code constants. You can view built-in key code constants by opening the Module window and pressing F2 to display the Object Browser. Key code constants are displayed as members of the Constants class in the Access type library. Alternatively, you can declare constants for the values in your SendKeys statement.

Defining your keystrokes as constants makes updating your code easier in the future.
Do not enclose the Keystroke argument in quotation marks.

In Access 2.0, you can enclose the Keystrokes argument of the SendKeys action in quotation marks, but it is not required. If you enclose this argument in quotation marks in subsequent versions of Access, however, an error occurs. To use quotation marks in the Keystrokes argument, you must type two sets of quotation marks, as in Michael ""Mick"" Suyama.

Using the DoCmd Object

To carry out macro actions from code in Access 97, use the DoCmd object and its methods. This object replaces the DoCmd statement that you used in Access 1.x and 2.0 to carry out a macro action.

When you convert a database, Access automatically converts any DoCmd statements and the actions that they carry out in your Access Basic code to methods of the DoCmd object by replacing the space with the dot ( . ) operator.

Using the TransferSpreadsheet and TransferText Actions

Access 97 cannot import Excel version 2.0 spreadsheets or Lotus 1-2-3 release 1.0 spreadsheets. If your converted database contains a macro that provides this functionality by using the TransferSpreadsheet action in Access 1.x or 2.0, converting the database changes the Spreadsheet Type argument to Excel version 3.0 (if you originally specified Excel version 2.0) or causes an error if you originally specified Lotus 1-2-3 1.0 format.

To work around this problem, convert the spreadsheets to a later version of Excel or Lotus 1-2-3 before importing them into Access.

Also, in Access 97, you cannot use an SQL statement to specify data to export when you are using the TransferText action or the TransferSpreadsheet action. Instead of using an SQL statement, you must first create a query and then specify the name of the query in the Table Name argument.

Access Basic Code Changes

In Access 97, Visual Basic replaces Access Basic. In most respects, Visual Basic is identical to Access Basic, and Access automatically makes most of the necessary conversions to your code when you convert your database.

However, the conversion process makes some changes to your code that you need to be aware of, and there are some additional changes that you must make yourself in order for your application to run successfully in Access 97.

16-bit DLLs

If your database application calls procedures in other 16-bit DLLs, you must create or obtain 32-bit versions of those DLLs and make any necessary modifications to your code when you convert your database to Access 97.

If you cannot obtain a 32-bit version of a DLL, use an intermediary DLL that can convert 32-bit calls to 16-bit calls. For more information, see "Windows Application Programming Interface" later in this chapter.

ActiveX Controls

If your application contains ActiveX controls (formerly OLE control or custom controls) that were set up in Access 2.0, you may need to insert the ByVal keyword in front of arguments that are passed to event procedures called from ActiveX control events, as in the following example:

Sub ChangeMonth_Click(ByVal intCurrentYear As Integer)

In order to determine whether an argument needs to be passed by value, click Compile All Modules (Debug menu) in module Design view. If you receive the following message, you need to insert the ByVal keyword in front of the argument: "Event procedure declaration doesn't match description of event having the same name."

Because type checking of arguments is improved in Access 97, new event procedures created for ActiveX controls automatically have the ByVal keyword inserted when it is needed.

ActiveX Controls on Forms and Reports

When you convert an Access 2.0 database for use in Access 97, ActiveX controls on forms and reports may not be converted automatically. Access 2.0 supports 16-bit OLE controls, while Access 97 supports only 32-bit ActiveX controls.

If you are converting a database that contains a form or report that has a 16-bit version of an ActiveX control, and the 32-bit version does not yet exist on your system, Access generates an error message. You must obtain a 32-bit version of each ActiveX control that you wish to update and then enter it in the Windows registry. After you register the new ActiveX control, save the form or report in the converted database and then close and reopen the database.

Automation Errors

In Access 1.x and 2.0, ActiveX components that support Automation (formerly OLE Automation) return a generic error. However, Visual Basic now allows an ActiveX component to return error information specific to the error that has occurred. If your existing databases include code to handle a generic Automation error, you may have to update that code to handle the more specific errors that are now returned.

Category Property

You cannot use an object variable in your code to refer to a Category property. The Category property is no longer supported for Form, Report, and Control objects.

CurDir Function

The CurDir function behaves differently in Access 97 than it does in Access 1.x or 2.0 due to the way that applications interact with Windows 95. Since each application has its own current folder, setting the current folder in Windows 95 by double-clicking an icon does not affect the current folder in Access. The CurDir function in Access 97 always returns the current path.

CurrentDb Function Compared to DBEngine(0)(0)

Use the CurrentDb function instead of DBEngine(0)(0) to return a Database object variable that points to the current database. The CurrentDb function creates another instance of the current database, while DBEngine(0)(0) refers to the open copy of the current database. If you use DBEngine(0)(0), it limits your ability to use more than one variable of type Database that refers to the current database.

The DBEngine(0)(0) syntax is still supported in Access 97, so your code does not change during the conversion process. However, it is recommended that you consider making this modification to your code in order to avoid possible conflicts in a multiuser environment.

DAO Object Libraries

Access 97 includes Data Access Objects (DAO) objects, methods, and properties that replace those in Access 1.x, 2.0, and 95. While the code in Access 97 is compatible with all previous DAO code, future versions of Access may not provide support for some older objects, methods, and properties. The following sections explain how to take advantage of the backward-compatibility features in Access 97, as well as how to create new applications and modify current applications to prepare for converting to future versions of Access.

Taking Advantage of Backward-Compatibility Features

If you want to continue to use the older versions of DAO objects, methods, and properties in your application, you must first establish a reference to the DAO version 2.5/3.5 compatibility library.

To establish a reference to the DAO version 2.5/3.5 compatibility library

Switch to module Design view.
On the Tools menu, click References.
In the Available References box, click Microsoft DAO version 2.5/3.5 Compatibility Library.

The Microsoft DAO 2.5/3.5 compatibility library provides complete backward compatibility with Access 1.x, 2.0, and 95. A reference to this version of the library is added to Access 1.x, 2.0, and 95 applications that you convert to Access 97.

The Microsoft DAO 3.5 object library, which does not include the older objects, methods, and properties, is selected by default whenever you create a new database. All new applications created in Access 97 should reference only the Microsoft DAO 3.5 object library to ensure the application is not using old methods. Also, if your application references only the Microsoft DAO 3.5 object library, you do not have to distribute the Microsoft DAO 2.5/3.5 compatibility library when you distribute your application to other users.

Tip To verify that your application only uses the objects, methods, and properties in the Microsoft DAO 3.5 object library, clear the Microsoft DAO 2.5/3.5 Compatibility Library check box in the References dialog box (Tools menu). Make sure that Microsoft DAO 3.5 Object Library is selected, and then recompile your application by clicking Compile All Modules (Debug menu) in module Design view. If your application recompiles without errors, you no longer need to maintain the reference to the Microsoft DAO 2.5/3.5 compatibility library, and your application will work with the next version of DAO.

Preparing for Conversion to Future Versions

The following table lists the objects, methods, and properties that are not included in the Microsoft DAO 3.5 object library, as well as the features that have been provided to replace them. You can use the new items in the second column to modify code written in previous versions of Access, so that your application is prepared for conversion to future versions of Access, when the items in the first column are no longer available.

Functionality not present in DAO 3.5	Recommended DAO 3.5 replacements
FreeLocks	Idle method of the DBEngine object (not needed for Access 95 and 97 databases)
SetDefaultWorkspace	DefaultUser/DefaultPassword properties of the DBEngine object
SetDataAccessOption	IniPath property of the DBEngine object
Database. BeginTrans	Workspace. BeginTrans
Database. CommitTrans	Workspace. CommitTrans
Database. CreateDynaset	Database. OpenRecordset of type dbOpenDynaset
Database. CreateSnapshot	Database. OpenRecordset of type dbOpenSnapshot
Database. DeleteQueryDef	Delete method of the QueryDefs collection
Database. ExecuteSQL	Database. Execute method and Database.RecordsAffected property
Database. ListTables	Database. TableDefs collection
Database. OpenQueryDef	Database. QueryDefs collection
Database. OpenTable	Database. OpenRecordset of type dbOpenTable
Database. Rollback	Workspace. Rollback
ListFields method of the Table, Dynaset, and Snapshot objects	Recordset. Fields collection
Table. ListIndexes	TableDef. Indexes collection
QueryDef. CreateDynaset	QueryDef. OpenRecordset
QueryDef. CreateSnapshot	QueryDef. OpenRecordset
QueryDef. ListParameters	QueryDef. Parameters collection
Dynaset object	Dynaset-type Recordset object
Snapshot object	Snapshot-type Recordset object
Table object	Table-type Recordset object
CreateDynaset method of the Dynaset and QueryDef objects	Recordset. OpenRecordset with dbOpenDynaset parameter
CreateSnapshot method of the Dynaset and QueryDef objects	Recordset. OpenRecordset with dbOpenSnapshot parameter

For examples of how to modify your code, see the Access online Help.

Database Renaming

When you rename a database, compiled code in the database is decompiled. To recompile code and save all modules in a compiled state, open the database, open a module in Design view, and then click Compile and Save All Modules (Debug menu).

DDE Channels Declared as Variant or Long

If you use the DDEInitiate function to open a dynamic data exchange (DDE) channel, you can declare the variable that stores the channel number, which is a Long value, as either a Variant or a Long value. In Access 1.x and 2.0, the channel number is an Integer value, so you must modify any Declaration statements in your code that create variables of type Integer to store the channel number.

Error Information

In Access 95 and 97, you cannot use the Error function to return a description of Access errors. For example, the following reference does not work:

Error(2450)

In Access 97, use the properties of the Err object to obtain information about errors.

When an Access error occurs, you can get the error number and the error description by using the Number and Description properties of the Err object , as in the following example:

Debug.Print Err.Number, Err.Description

To return information about Access, Visual Basic, or DAO errors, use the AccessError method. With the AccessError method, you can obtain error information regardless of whether the error has actually occurred.

Exclamation Point Compared to Dot Operator

If you used the dot ( . ) operator syntax when referring to a Field object of a Recordset object in applications created in Access 1.x or 2.0, you must modify those references to use the exclamation point ( ! ) operator syntax. Or, if you want to continue using the dot ( . ) operator syntax, you must establish a reference to the DAO 2.5/3.5 compatibility library in the References dialog box (Tools menu) while in module Design view.

Functions Not Supported in Expressions

The following Visual Basic functions cannot be used in expressions outside a user-defined Sub or Function procedure:

EOF
Loc
FileAttr
LOF
FreeFile
Seek

If you need to use one of these functions in an expression outside a procedure, call the function from within a user-defined function that you call from the expression.

hWnd Property

If you use the hWnd property in your code to pass a window handle of a form or a report to a Windows routine, you can pass the value directly to the routine. You do not need to assign the value of this property to a variable. For example:

If Not IsZoomed(Screen.ActiveForm.hWnd) Then 
DoCmd.Maximize 
EndIf

In Access 1.x and 2.0, the hWnd property of a form or report is an Integer value. In Access 97, the hWnd property is a Long value; you must change your code to accept it.

Line Numbers in Visual Basic Procedures

You cannot assign line numbers greater than 65,529 to statements in your Visual Basic procedures. If your converted Access 1.x or 2.0 application contains line numbers greater than 65,529, you must modify them to fall within the acceptable range.

Microsoft Access Wizards

Code in your Access 1.x or 2.0 application may call procedures that are located in Access wizards. If this is the case, you must, after you convert the application, establish a reference from the application to the wizard database that contains the procedures that you call. For more information about establishing references, see Access online Help.

In Access 2.0, there is no distinction between wizards and libraries, so their public code is always available to the current database. In Access 97, wizards and other add-ins are no longer treated as libraries. In addition, because wizards may change a great deal from one version of Access to the next, you may need to rewrite some of your code to adapt to the changes after upgrading to a new version of Access.

For code that is no longer provided in the Access wizards, such as the AutoDialer, functionality has been added to Utility.mda, a special library database that is provided with Access. A reference to this library is automatically added when you convert a database to Access 97.

Module Changes

In Access 1.x and 2.0, modules containing procedures that are not specific to any form or report module are called global modules. In Access 97, these are called standard modules.

In Access 97, form and report modules are now called class modules, which means that they can act as templates for a user-defined object. Any public procedures in a form or report module become methods and properties of the new form or report when you create a new instance of it. For more information about class modules, see the Access online Help.

Next Procedure and Previous Procedure Buttons

The Next Procedure and Previous Procedure buttons on the Module toolbar in Access 1.x and 2.0 are not available in Access 97. If you convert an Access 1.x or 2.0 database with a custom toolbar that contains one of these buttons, you do not receive an error, but the buttons have no effect when clicked.

Null Values and Zero-Length Strings

In Access 2.0, you can use the Format function to return one value for a zero-length string and another for a Null value, and you can similarly use the Format property to automatically format fields in table Datasheet view or controls on a form or report. For example, you can use a format expression such as the following with the Format function to return the appropriate string value from code:

Dim var As Variant, strX As String 
' Assign some value to strX and pass to Format function. 
var = Format(strX, "@;ZLS;Null")

In Access 97, you must test separately for the Null value case and then return the appropriate value based on the result. For example, you could use the IIf function in an expression with the Format function, such as the following:

var = IIf(IsNull(strX),"Null", Format(strX, "@;ZLS"))

This change applies only when you use the Format function to format a value depending on whether it is a zero-length string or a Null value. Other format expressions used with the Format function continue to work as they do in previous versions of Access.

If you convert a database from Access 2.0 to Access 97, you must change any code or property settings to use these methods. You cannot use the Format property in table Datasheet view to distinguish between Null values and zero-length strings.

Objects in the Debug Window

When you are testing and debugging code, you must fully qualify all references to objects that you use in the Debug window, unless you have suspended execution in a form or report module. This means that in the Immediate pane of the Debug window, you must use the code Forms!Categories!CategoryID to refer to the CategoryID control on the Categories form in Form view, instead of just CategoryID, even when the Categories form is the current form.

Also, you cannot use the Me keyword in the Debug window to refer to an object on a form or report when that form or report is in Design view unless you have suspended the execution of code in the form or report.

OLE Objects Assigned to a Variable

If you manipulate OLE objects or other binary data in your code, use an array of bytes to store binary data. In Access 1.x and 2.0, you assign OLE objects, or other binary data less than 64 KB in size, to string variables when you need to manipulate the objects or data in code. You also assign the data returned by the GetChunk method to string variables. However, Visual Basic supplies a Byte data type and Byte functions such as LeftB and RightB. In Access 97, store binary data in an array of bytes instead of a string variable, and use the Byte functions to manipulate that data.

Parent Property

In Access 97, if you use the Parent property of a control in code or in an expression on a form or report, it typically returns the Form or Report object that contains the control. For example, if CategoryID is a text box on the Categories form, the code Forms!Categories!CategoryID.Parent returns a reference to the Categories form.

There are two exceptions:

For attached labels, the Parent property now returns the control to which the label is attached.
For controls in an option group, the Parent property now returns the option group control.

Percent Sign (%) in Strings

You cannot assign a string containing a percent sign (%) to a variable or a field that has a numeric data type, as in the following example:

Dim intX As Double 
intX = "10" ' This works. 
intX = "10%" ' This returns an error.

Procedures in Form and Report Modules

In Access 1.x and 2.0, you cannot call a procedure defined in a form or report from anywhere but within that form or report module. In Access 97, you can call a public procedure in a form or report module from any procedure in the current database. You must qualify the procedure with the class name of the form or report module. For example, to call a procedure named DisplayMessage that is defined in the module of the Orders form, use the following syntax:

Form_Orders.DisplayMessage

It is better to place procedures that you call from outside a form or report in a standard module if possible, rather than in a form or report module.

Reference to a Microsoft Access Database

You cannot set a reference to a database created with a previous version of Access from Access 97. You must convert the database to an Access 97 database in order to set a reference to it. For information about converting databases, see "Converting Databases" earlier in this chapter.

Time Values in Query Criteria

When you convert an Access 1.x or 2.0 database to Access 97, queries that contain criteria based on specific time values in Date/Time fields may return different results than they do in previous versions. This behavior may also occur if you link tables from an Access 1.x or 2.0 database to an Access 97 database. Only the time portion of Date/Time fields is affected.

Visual Basic Scoping and Object Naming

The following Visual Basic scoping rules affect the names you choose for your objects, modules, and procedures.

Modules and Other Objects with the Same Name

When you name a module, avoid prefacing module names with "Form_" or "Report_". Naming a module in this way could conflict with existing code you have written behind forms and reports.

If you have a module in an application from Access 1.x or 2.0 that does not follow these naming rules, Access 97 generates an error when you try to convert the application. For example, a module named Form_Orders in an Access 1.x or 2.0 database generates an error, and you are asked to rename the module before attempting to convert it.

Modules and Procedures with the Same Name

A procedure can have the same name as a module. However, to call that procedure from an expression anywhere in your application, you must use a fully qualified name for the procedure, including both the module name and the procedure name, as in the following example:

IsLoaded.IsLoaded("Orders")

Procedures and Controls with the Same Name

If you call a procedure from a form, and that procedure has the same name as a control on the form, you must fully qualify the procedure call with the name of the module in which it resides. For example, if you want to call a procedure named PrintInvoice that resides in a standard module named Utilities, and there is also a button on the same form named PrintInvoice, use the fully qualified name — Utilities.PrintInvoice — when you call the procedure from your form or form module.

Controls with Similar Names

A control's name must not differ from an existing control's name by only a space or a symbol. For example, if you have a control named [Last_Name], you cannot have a control named [Last Name] or [Last+Name].

Modules with the Same Names as Type Libraries

You cannot save a module with the same name as a type library. If you try to save a module with the name DAO, Access, or VBA, a message is generated, stating that the name conflicts with an existing module, project, or object library. Similarly, if you have set a reference to another type library, such as the Excel type library, you cannot save a module with the name Excel.

Fields with the Same Names as Methods

If a field in the table has the same name as a DAO method on a Recordset object, you cannot refer to the corresponding field in the recordset with the dot ( . ) operator syntax. You must use the exclamation point ( ! ) operator syntax, or Access generates an error. The following example shows how to refer to a field called AddNew in a recordset opened on a table called Contacts:

Dim dbs As Database, rst As Recordset 
Set dbs = CurrentDb 
Set rst = dbs.OpenRecordset("Contacts") 
Debug.Print rst!AddNew

Modules with the Same Names as Visual Basic Functions

If you save a module with the same name as an intrinsic Visual Basic function, Access generates an error when you try to run that function. For example, if you save a module named MsgBox, and then try to run a procedure that calls the MsgBox function, Access generates the error "Expected variable or procedure, not module."

Modules with the Same Names as Objects

If a database created in a previous version of Access includes a module that has the same name as an Access object or a DAO object, you may encounter compilation errors when you convert your database to Access 97. For example, a module named Form or Database may generate a compilation error. To avoid these errors, rename the module.

Fields Used in Expressions or Bound to Controls on Forms and Reports

When you create a field in a table that is bound to a control on a report or used in an expression in the ControlSource property of a control or a report, avoid assigning the field a name that is the same as a method of the Application object. To see a list of methods of the Application object, click Object Browser (View menu) while in module Design view. Click Access in the Project/Library box, click Application in the Classes box, and then view the methods of the Application object in the Members Of box.

When you create a field in a table that is bound to a control on a form or report, avoid assigning the field any of the following names:

AddRef
GetIDsOfNames
GetTypeInfo
GetTypeInfoCount
Invoke
QueryInterface
Release

These are the names of methods used internally by Access to work with forms and reports. If you use them as names for fields, they could cause conflicts or unexpected behavior when referenced in expressions or Visual Basic code.

Identifiers with the Same Names as Visual Basic Keywords

The version of Visual Basic that is used by Access 97 contains some new Visual Basic keywords, so you can no longer use these keywords as identifiers:

AddressOf
Assert
Decimal
DefDec
Enum
Event
Friend
Implements
RaiseEvent
WithEvents

When you convert or enable a database from a previous version of Access, existing identifiers that are the same as a new Visual Basic keyword cause Access 97 to display the following message: "There were compilation errors during the conversion or enabling of this database." This message is displayed, for example, if you try to enable or convert the Northwind Traders sample database from Access 2.0. This is because the ShowEvent Sub procedure in the Utility Functions module uses Event as a string variable.

To correct this problem, open the module that contains the code that uses one or more of the new keywords as identifiers and rename them. For example, after converting the Northwind Traders database, open the Utility Functions module, and change the Event string variable name throughout the procedure to another name, such as strEvent.

Windows Application Programming Interface

If your existing Access 1.x or 2.0 Access Basic code makes calls to the Windows application programming interface (API), you must modify these calls when you convert your database to Access 97. Access 1.x and 2.0 are 16-bit applications and run on 16-bit versions of Windows. Access 97 is a 32-bit application and runs on the 32-bit Windows 95 and Windows NT operating systems.

The Windows API consists of a set of DLLs containing system-related procedures that include functions, messages, data structures, data types, and statements you can use in creating applications that run under Windows 95 or Windows NT operating system. To call these procedures from Visual Basic, you must first declare them with a Declare statement. You can then call them as you would any other procedure.

The following list provides some tips for converting your code:

Check any Declare statements to ensure that they refer to the correct DLLs.

16-bit Windows DLL

32-bit Windows DLL

User.dll

User32.dll

Kernel.dll

Kernel32.dll

GDI.dll

GDI32.dll
Check to make sure that you have entered the procedure name and alias name correctly.

The names of some functions in the 32-bit Windows API have changed. Additionally, functions in the 32-bit Windows API are case-sensitive.
Consult one of the references listed later in this section to determine the function calls you must update.

Some functions have new parameter data types in the 32-bit Windows API.
Check for 16-bit DLLs with the same name as 32-bit DLLs.

If a 16-bit version of a DLL with the same name as a 32-bit DLL exists on your computer, Access may try to call a function in that DLL if your path lists its folder before the folder that contains the new DLL.
If the function takes string-type arguments, try appending an a or w to the function name.

Some 32-bit DLLs contain functions with slightly different versions to accommodate both Unicode and ANSI strings. An a at the end of the function name specifies the ANSI version. A w at the end of the function name specifies the Unicode version.

16-bit Windows DLL	32-bit Windows DLL
User.dll	User32.dll
Kernel.dll	Kernel32.dll
GDI.dll	GDI32.dll

For more information about using 32-bit Windows API procedures and about porting your existing database applications to 32-bit Access 97, consult the following resources:

"Porting Your 16-bit Office-Based Solutions to 32-bit Office" in Chapter 10, "Upgrading from Previous Versions of Microsoft Office."
The Win32 API Viewer, available in Microsoft Office 97 Developer Edition. The viewer includes Visual Basic syntax for all 32-bit declarations, data types, and constants.
The Microsoft Win32 Software Development Kit. This kit provides complete reference information for 32-bit Windows API procedures.

World Wide Web For the latest information about modifying 16-bit calls for 32-bit Office in Access, connect to the Access Developer Web site at:
https://msdn.microsoft.com/library/default.asp?url=/nhp/default.asp?contentid=28000550

Custom menus and shortcut menus created in a previous version of Access are handled differently. Previous versions of Access use the Menu Builder to create custom menus and shortcut menus. The Menu Builder generates a macro group containing macros that use the AddMenu and DoMenuItem actions. In previous versions of Access, you can also create custom menus and shortcut menus manually (without the Menu Builder) using these macro actions. Custom menu and shortcut menu macros created using either method still run Access 97, but they are not converted to the new style, nor are they available from the new Customize dialog box (View menu, Toolbars submenu).

Upgrading from MS Access 1.x

This section describes the differences between Access 1.x and Access 97. Access 97 is a major upgrade from previous versions of the application. For more information about the features and benefits of this upgrade, see Chapter 2, "What's New in Microsoft Office."

What happens to my old Access databases when I convert them to Access 97 format? You can open databases created in Access 1.x directly in Access 97, even if you do not convert the database using a process called enabling. Once you convert an Access 1.x database to Access 97 format, you cannot open it in Access 1.x, and it cannot be converted back to Access 1.x format.

Can I share Access 97 databases with users of previous versions of Access? If your workgroup is using a combination of Access 97 and 1.x, users can share data and databases. However, not all Access 97 features are supported in previous versions.

Do my old macros still work in Access 97? In most cases, macros created in Access 1.x run in Access 97. If you convert or enable an Access 1.x database containing macros in Access 97, the macros run in Access 97.

Does my old Access Basic application code still work in Access 97? In most cases, Access Basic application code created in Access 1.x runs in Access 97. If you convert an Access 1.x database to Access 97, the Access Basic code is converted to equivalent Visual Basic code. If you enable an Access 1.x database in Access 97, a copy of the Access Basic code is converted to equivalent Visual Basic code; your original code is not altered.

Note All of the conversion issues that apply when you upgrade from Access 2.0 also apply to opening and running an Access 1.0 or 1.1 database in Access 97. The following section addresses issues that apply only to opening and running Access 1.x databases in Access 97.

Access Basic Code Changes

In Access 97, Visual Basic for Applications replaces Access Basic. In most respects, Visual Basic is identical to Access Basic, and Access automatically makes most of the necessary conversions to your code when you convert your database.

However, the conversion process makes some changes to your code that you need to be aware of, and there are some additional changes that you must make yourself in order for your Access 1.0 and 1.1 application to run successfully in Access 97.

Backquote Character (`) in Object Names

If an object name in an Access 1.x database includes a backquote character (`), you cannot open that object using Access 97 or convert the database to Access 97 format. Rename the object in Access 1.x, and then change references to that object in your queries, forms, reports, macros, and modules. Use the Documenter command (Tools menu, Analyze submenu) to find occurrences of the old name in your references.

Combo Boxes and List Boxes

For combo boxes and list boxes that have their RowSource property set to a table or a query, Access 97 displays data in the rows of the combo or list box by using the format defined for the data in the Format property of the underlying field. Access 1.x, by contrast, does not use the Format property of the underlying field.

Query Fields

In Access 97 your queries and the forms based on them are less restrictive than in Access 1.x. Using Access 97, you can update the data in some fields in multiple-table queries that you cannot update using Access 1.x. For example, in a query that includes fields from a Customers table and an Orders table (where one customer can have more than one order), you cannot update fields from the Customers table using Access 1.x. Using Access 97, however, you can update fields from the Customers table in most situations. If you do not want users to update such fields in a form, use Access 1.x to set the Locked property to Yes for form controls that are bound to the fields.

Validation Rules for Tables

In Access 97, validation rules you set for fields and records in a table protect your data regardless of how it is entered or modified: whether by using a datasheet or form, importing data, using action queries, or carrying out Visual Basic commands. If you have the same validation rule set for both a field in a table and a control on a form that is bound to that field in an Access 1.x database, after converting the database, you can delete the rule set for the control.

If your Access 1.x database validation rules contain elements not allowed in Access 97, the rules are not converted to Access 97 format. When Access encounters invalid validation rules while converting your Access 1.x database, it creates the ConvertErrors table in the converted database with information to help you fix the rules.

Visible Property

In Access 1.x, setting the Visible property of a control to No makes the control invisible in Form view and also hides its column in Datasheet view. In Access 97, the Visible property does not hide a control's column in Datasheet view. If you want to hide a column in Access 97, click the Hide Columns command (Format menu).

If your workgroup is upgrading gradually to Access 97, some users may need to share databases with users of Access 1.x, 2.0, or 95. There are two strategies for sharing databases between different versions of Access:

Open the database in its existing format, which is called enabling the database.
Create a front-end database in Access 97 format that is linked to table data in a back-end database from a previous version of Access.

The following table summarizes the advantages and disadvantages of each strategy.

Strategy	Advantages	Disadvantages
Enable previous version databases	All Access users can open databases and add, edit, or delete data.	Database file size can increase substantially. Access 97 users cannot modify or add new objects, or take advantage of many features unique to Access 97.
Create a front-end database in Access 97 format linked to table data in a back-end database from a previous version of Access	All Access users can open databases and add, edit, or delete data. Access 97 users can modify or add new objects, (except tables) and can take advantage of features unique to Access 97.	Additional development of the front-end databases must be synchronized. Changes made to the front-end database in Access 97 must be repeated in the back-end database. Features unique to Access 97 are not supported in the older version back-end database.

Enabling a Database

Enabling a database keeps the format intact so it can be shared by users of different versions of Access. When an Access 97 user enables an Access 1.x, 2.0, or 95 database, other users can browse the database and add, delete, or modify records; but they cannot switch to Design view on any objects. To modify the design of existing objects or to add new objects, the database must be opened in the version of Access used to create it.

Note Before you enable a database, make sure it is not open in a previous version of Access. If the database is located on a server or shared folder, make sure no one else has it open. Finally, if you have a database open in Access 97, close it.

To enable an Access 1.x, 2.0, or 95 database

On the File menu, click Open Database.
In the Open dialog box, select a database.

The first time a database from a previous version of Access is opened, Access 97 displays the Convert/Open Database dialog box.
Click Open Database to open the database without converting it.

If the database contains forms, reports, and modules, Access 97 creates separate copies of these objects and their Access Basic (Access 1.x or 2.0) or Visual Basic (Access 95) code so that they can run under Access 97. This information is stored in a hidden table named MSysModules2. Depending on the size of the forms, reports, and modules in the database, the addition of the MSysModules2 table can increase the file size by as much as double. If an Access 1.x or 2.0 database has been enabled previously by Access 95, it has a similar table named MSysModules, which further increases the size of the database.

Access 97 does not display the Convert/Open Database dialog box the next time the database is opened unless a change is made to code in modules, forms, or reports in the previous version of Access. If a change has been made to the code, you must enable the database again.

You can speed up the process of enabling a large database created with Access 1.x or 2.0 by increasing the maximum buffer size beyond the default. To change this setting, modify the Windows registry by setting the MaxBufferSize value to 4096, decimal base in the key HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \Jet \3.5\Engines\Jet 2.x. For more information about editing the Windows registry, see Appendix C, "Registry Keys and Values."

Creating a Front-end Database Linked to Table Data in a Previous Version Back-end Database

Enabling a database as described in the previous section places limitations on Access 97 users, increases the size of the database, and requires additional memory, particularly when running code. As an alternative, you can split the database into an Access 97 front-end database that contains all objects other than tables, and then link this database to a shared back-end database in the older version format. The back-end database contains the tables.

In general, it is good practice for developers to keep application code and objects in a separate database from the tables. This allows administrators to convert a copy of the front-end database to Access 97 format while leaving the back-end database containing the tables in the previous version format until all users have upgraded to Access 97. In this way, the converted copy of the front-end database gains all the features and functionality of Access 97, yet the back-end database containing the tables is still available to all users.

Many developers who use previous versions of Access organize shared databases as front-end/back-end databases. If this is the case for you, convert a copy of the front-end database and distribute it to all Access 97 users, and then use the Linked Table Manager (Tools menu, Add-ins submenu) to relink the tables in the back-end database. If the current database has not been split in this fashion, you can do so in the previous version of Access, and then convert the front-end database.

You can also use Access 97 to split the database and link to the older version tables. In Access 97, convert the database, split it using the Database Splitter Wizard, and then use the Linked Table Manager (Tools menu, Add-ins submenu) to relink the original tables in the previous version database.

Note Before you create and link a front-end database, make sure the linked database is not open in a previous version of Access. If the database is located on a server or shared folder, make sure no one else has it open. Finally, if you have a database open in Access 97, close it.

To create an Access 97 front-end database

In Access 97, point to Database Utilities on the Tools menu, and then click Convert Database.
In the Database to Convert From dialog box, select the database, and then click Convert.
In the Convert Database Into dialog box, type a new name (without the .mdb extension) for the Access 97 database.

– or –

Select a different location for the Access 97 database, and then click Save.

Access creates a converted copy of the database in Access 97 format without altering the original database. Then you can link the copy of the database to the original table data.

To link a front-end database to table data in a back-end database from a previous version of Access

On the Tools menu, point to Add-ins, and then click Database Splitter.
Follow the instructions in the Database Splitter Wizard.
Delete the back-end database created by the Database Splitter Wizard, and then open the converted front-end database.
On the Tools menu, point to Add-ins, and then click Linked Table Manager.
Select the Always prompt for new location check box.
Select the check boxes for all the tables, and then click OK.
In the Select New Location of table name dialog box, specify the location of the previous version database, click Open, and then click OK.

Tip You can also open a new, blank database in Access 97. To import all objects except for tables into the new database, point to Get External Data on the File menu and click Import. Then link the tables from the previous version database by clicking Link Tables on the Get External Data submenu (File menu).

Chapter 11 - Upgrading from Previous Versions of MS Access

On This Page

Overview

Converting Databases

To convert a database

Why won't my database convert?

Converting Unbound Object Frame Controls to Image Controls

To convert unbound object frame controls to image controls when you convert a database

To convert unbound object frame controls to image controls after you convert a database

Converting a Database Secured with a Database Password

Converting a Database Secured with User-level Security

Joining the Original Workgroup Information File

To join a workgroup information file from a previous version of Access

Recreating Microsoft Access 1.x and 2.0 Workgroup Information Files

To create the new workgroup information file in Access 97

To recreate the user and group accounts for a workgroup information file

Converting a Replicated Database

To convert a replica set

Working with MS Access 1.x and 2.0 Databases with Attached ODBC Tables

To create a new, identically named 32-bit DSN

Upgrading from MS Access 95

Menu Changes

File Menu

Edit Menu

View Menu

Insert Menu

Run Menu

Debug Menu

Tools Menu

Window Menu

Help Menu

File Format Changes

Using the Same Table in Microsoft Access 95 and 97

Template Changes

Macro Changes

SendKeys Action

DoMenuItem Action

Visual Basic Code Changes

New Toolbars, Menus, and Shortcut Menus

Upgrading from MS Access 2.0

Menu Changes

File Menu

Edit Menu

View Menu

Insert Menu

Tools Menu

Relationships Menu

Query Menu

Format Menu

Records Menu

Macro Menu

Run Menu

Debug Menu

Window Menu

Help Menu

File Format Changes

Template Changes

Macro Changes

Using the SendKeys Statement or Action

Using the DoCmd Object

Using the TransferSpreadsheet and TransferText Actions

Access Basic Code Changes

16-bit DLLs

ActiveX Controls

ActiveX Controls on Forms and Reports

Automation Errors

Category Property

CurDir Function

CurrentDb Function Compared to DBEngine(0)(0)

DAO Object Libraries

Taking Advantage of Backward-Compatibility Features

To establish a reference to the DAO version 2.5/3.5 compatibility library

Preparing for Conversion to Future Versions

Database Renaming

DDE Channels Declared as Variant or Long

Error Information

Exclamation Point Compared to Dot Operator

Functions Not Supported in Expressions

hWnd Property

Line Numbers in Visual Basic Procedures