3 Migrating a Microsoft Access Application

Verifying If Generated DDL Executes Against the Appropriate Instance

When using Oracle SQL Developer Migration Workbench, you must verify that the generated DDL statements are executed against the same instance where Oracle Application Express 3.0 or later is installed. If you select a Least Privilege Schema Migration, the migrated objects can be created in an existing schema on your database instance. Otherwise, a schema of the same name as the captured database (for example, Northwind) is created on your database instance.The migrated Oracle database schema objects must be in the same instance where Oracle Application Express 3.0 is installed. If they are not, you will not be able to complete the next step.

Creating a Workspace Manually

To create an Oracle Application Express workspace manually:

1. Log in to Oracle Application Express Administration Services. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance. You log in using the ADMIN account and password created or reset during the installation process.

   1. In a Web browser, navigate to the Oracle Application Express Administration Services application. By default, Oracle Application Express Administration Services installs to the following location:

      • If your setup uses the embedded PL/SQL gateway, go to:

        http://hostname:port/apex/apex_admin
        

        Where:

        hostname is the name of the system where Oracle XML DB HTTP Server is installed.

        port is the port number assigned to Oracle XML DB HTTP Server. In a default installation, this number is 8080.

        apex is the database access descriptor (DAD) defined in the configuration file.

      • If your setup uses Apache and mod_plsql, go to:

        http://hostname:port/pls/apex/apex_admin
        

        Where:

        hostname is the name of the system where Oracle HTTP Server is installed.

        port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777.

        pls is the indicator to use the mod_plsql cartridge.

        apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.

   2. On the Login page:

      • In Username, enter admin.

      • In Password, enter the Oracle Application Express administrator account password you specified when you installed Oracle Application Express.

      • Click Login.

   See Also:

   See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.

   Next, create a workspace.

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Create Workspace.

   The Create Workspace Wizard appears.

4. For Identify Workspace, enter a workspace name and description and click Next.

5. For Identify Schema, select the Oracle Forms application schema.

   1. For Re-use existing schema, select Yes.

   2. Select a schema from the list.

   3. Click Next.

6. For Identify Administrator, enter the Workspace administrator information and click Next.

7. Confirm your selections and click Create.

Creating Oracle Application Express Users

To create an Oracle Application Express user account:

1. Log in to Oracle Application Express Administration Services. See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.

2. Click Manage Workspaces.

3. Under Manage Workspaces, click Manage Developers and Users.

   The Manage Developers and Users page appears.

4. Click Create.

   The Create/Edit User page appears.

5. Under User Attributes, enter the appropriate information. Fields marked with an asterisk are required.

   Tip:

   To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark.

6. Under Password, type a case-sensitive password for this account.

   If your organization has set up a password policy, be sure the password meets the requirements.

7. Under Developer Privileges, select the appropriate privileges:

   • User is a developer - To add this user as a developer, select Yes. For end users, select No.

     Developers can create and modify applications and database objects as well as view developer activity, session state, workspace activity, application, and schema reports.

   • User is a workspace administrator - To add this user as a Workspace administrator, select Yes. For developers or end users, select No.

     In addition to having developer privileges, workspace administrators can create and edit user accounts, manage groups, alter passwords of users within the same workspace, and manage development services.

8. Under Account Control, specify the following:

   • Account Availability - Select Unlocked to enable a user to log in to this account.

   • Require Change of Password on First Use - Select Yes to require the user to change the password immediately after logging in with the current, temporary password. Otherwise, select No.

9. Click Create User or Create and Create Another.

Logging in to Your Oracle Application Express Workspace

Once you create a workspace, you must log in to it using your login credentials (that is, the workspace name, user name, and password).

To log in to a workspace:

1. In a Web browser, navigate to the Oracle Application Express Login page. By default, Oracle Application Express installs to the following location:

   • If your setup uses the embedded PL/SQL gateway, go to:

     http://hostname:port/apex
     

     Where:

     • hostname is the name of the system where Oracle XML DB HTTP Server is installed.

     • port is the port number assigned to Oracle XML DB HTTP Server. In a default installation, this number is 8080.

     • apex is the database access descriptor (DAD) defined in the configuration file.

       For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.

   • If your setup uses Oracle HTTP Server (Apache) and mod_plsql, go to:

     http://hostname:port/pls/apex
     

     Where:

     • hostname is the name of the system where Oracle HTTP Server is installed.

     • port is the port number assigned to Oracle HTTP Server. In a default installation, this number is 7777. You can find information about your Oracle HTTP Server installation's port number from either of the following files:

       ORACLE_BASE\ORACLE_HOME\install\portlist.ini
       ORACLE_BASE\ORACLE_HTTPSERVER_HOME\Apache\Apache\conf\httpd.conf
       

       Be aware that if you change a port number, it is not updated in the portlist.ini file. You can only rely on this file immediately after installation.

     • pls is the indicator to use the mod_plsql cartridge.

     • apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.

       For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.

   The Login page appears.

2. Under Login, enter the following:

   • In the Workspace field, enter the name of your workspace.

   • In the Username field, enter your user name.

   • In the Password field, enter your case-sensitive password.

3. Click Login.

   Note that, depending on your setup, you might be required to change your password when you log in for the first time.

About the Project Page

The project page initially shows a high-level overview of the Microsoft Access objects retrieved from your Microsoft Access database.

Specifically, the project page shows the status of these objects in your database:

• tables

• queries (now oracle views)

• forms

• reports

Additionally, for reference purposes only, the project page shows:

• databases

• modules

• pages

Note that your project might not include all object types. The project page lists only object types that exist in your database.

After you generate applications from this migration project, an application list is created on the project page. To review the list, click Applications. This opens the list box where you can review application information or run an application.

Reviewing Retrieved Tables

Next, review the Oracle tables retrieved from the Microsoft Access database. Application Migration identifies invalid tables without primary keys as well as those without user interface defaults, which you can add before migrating.

After you update the tables, select the ones you want to include in the migration. If you do not include a table, all forms and reports based on the table are excluded from the migration.

To review retrieved tables:

1. From the project page, click Tables.

   The Tables page appears, showing the status of the objects ready for migration.

   
   Description of the illustration acmg_tbl_pg.gif
   
   

   For each Microsoft Access table, the Tables page shows:

   • Oracle Table - The corresponding Oracle table, which defaults to the Microsoft Access table name in all capital letters.

     Note that the name might also differ from the original one because of the collision management facility in Oracle Migration Workbench. For information about naming guidelines and restrictions, click Help in Oracle Migration Workbench and go to the Frequently Asked Questions section.

     If the Microsoft Access object was not successfully migrated to Oracle, then this field will not have a corresponding Oracle table name. Instead, it will contain a link to a page where you can create a corresponding Oracle table.

   • Primary Key - Indicates if a primary key exists for the table.

     A table without a primary key is considered invalid in Application Migration. You can create a primary key at this point. All tables you want to migrate should have a primary key.

   • Foreign Key - Indicates if a foreign key exists for the table.

     If you know a relationship exists between two tables, you should create a foreign key. You can do this in Object Browser by creating a Foreign Key Constraint. For more information, see Table 16-1 in "Browsing a Table" Oracle Application Express Application Builder User's Guide.

   • UI Defaults - Indicates if user interface defaults are set for the table.

     User interface defaults are used by Oracle Application Express to populate initial values for region and item properties. Using user interface defaults provides consistency across multiple applications or across multiple pages in an application.

   • Status - Table status as either Valid or Invalid.

     Only valid tables can be included in the migration.

2. To create a table:

   1. On the Tables page, click the link in the Oracle Table column for the table you want to create.

      The Object Browser opens.

   2. Click the Create button.

   3. From the list of object types, select Table.

   4. Follow the on-screen instructions.

3. To add a primary key:

   1. On the Tables page, click the Oracle table name.

   2. In the Tasks list on the right, click Create Primary Key.

   3. For Constraint Details, fill in the information.

      
      Description of the illustration acmg_cr_prim_key.gif
      
      

      Tip:

      To review the list of existing columns or constraints, click the Existing Columns or Existing Constraints links.

   4. Click Next.

   5. Confirm the information and click Finish.

4. To add an index:

   1. On the Tables page, click the Oracle table name.

   2. In the Tasks list on the right, click Create Index.

   3. Select the type of index you want to create on this table.

      For indexing NUMBER, VARCHAR, and DATE, select Normal. For indexing CLOB columns, select Text.

      
      Description of the illustration acmg_cr_index.gif
      
      

   4. Click Next.

   5. For Index Definition, fill in the information.

      The following graphic shows the fields to fill out if you selected Normal as the type of index.

      
      Description of the illustration acmg_cr_index_norm.gif
      
      

      Tip:

      To review the list of existing table indexes or columns, click the Table Indexes or Table Columns links.

   6. Click Next.

   7. Confirm the information and click Finish.

5. To set user interface defaults:

   1. On the Tables page, click the Oracle table name.

   2. In the Tasks list on the right, click UI Defaults.

   3. On the UI Defaults page, click Create Defaults.

      The Table Defaults page appears, listing column information as it will appear in forms and reports. Note that you are now working within Application Builder, the component of Oracle Application Express where you can build and modify your applications.

   4. To edit the information, click Grid Edit. You can update the column label, change the sequence the columns will appear by default, and so on.

   5. Click Apply Changes to save your updates.

6. To include tables in the migration, select them in the left column.

7. Click Apply Changes to save your selections.

Reviewing Retrieved Queries

Next, review the queries retrieved from the Microsoft Access export. Application Migration identifies invalid queries as well as those without user interface defaults, which you can set before migration.

After you update the views, select the ones you want to include in the migration. If you do not include a query, any forms or reports based on the query are excluded from the migration.

To review retrieved queries:

1. From the project page, click Queries.

   The Queries page appears, showing the status of the objects ready for migration.

   
   Description of the illustration acmg_qry_pg.gif
   
   

   For each Microsoft Access query, the Queries page shows:

   • Oracle View - The corresponding Oracle view, which defaults to the Microsoft Access query name in all capital letters.

     If the Microsoft Access object was not successfully migrated to Oracle, then this field will not have a corresponding Oracle view name. Instead, it will contain a link to a page where you can create a corresponding Oracle view.

   • Status - Query status as either Valid or Invalid.

     Only valid queries can be included in the migration.

   • UI Defaults - Indicates if user interface defaults are set for the query.

     User interface defaults are used by Oracle Application Express to populate initial values for region and item properties. Using user interface defaults provides consistency across multiple applications or across multiple pages in an application.

2. To run a bulk process that attempts to compile all invalid queries, click Attempt to compile invalid queries.

   Using this option can validate some queries that show a status of invalid when initially migrated.

3. To create a view:

   1. On the Queries page, click the link in the Oracle View column for the view you want to create.

      The Object Browser opens.

   2. Click the Create button.

   3. From the list of object types, select View.

   4. Follow the on-screen instructions.

4. To edit a query:

   1. On the Queries page, click the Oracle view you want to edit.

   2. Click Compile to find the invalid part of the query.

      The Microsoft Access Query syntax appears in the edit window. It may require some modification to make it valid Oracle syntax.

   3. Click Access Query to review the initial query and compare it to the converted query.

   4. Click Edit.

   5. Update the query and recompile it.

   6. When it is validated, click the Queries breadcrumb.

   7. To include this validated query, select it in the left column on the Queries page and click Apply Changes.

5. To set user interface defaults:

   1. On the Queries page, click the Oracle view.

   2. In the Tasks list on the right, click UI Defaults.

   3. On the UI Defaults page, click Create Defaults.

      The Table Defaults page appears, listing column information as it will appear in forms and reports. Note that you are now working in Application Builder, the component within Oracle Application Express where you build and modify applications.

   4. To edit the information, click the Grid Edit button.

      You can update the column label, change the sequence the columns will appear by default, and so on.

   5. Click Apply Changes to save your updates.

   6. To return to the Application Migration, click the Home breadcrumb. Then, select the Application Migrations link on the right, select your migration project, and click Queries.

6. To include queries in the migration, select them in the left column.

7. Click Apply Changes to save your selections.

Reviewing Retrieved Forms

Next, review the forms retrieved from the Microsoft Access export. Application Migration identifies invalid forms and lists additional information, such as the form's source type and source name.

For valid forms with a source type of table, you can select the type of object you want the form to become within Oracle Application Express: form (default), report and form, or tabular form.

Microsoft Access forms based on a query are migrated to Oracle Application Express forms. Microsoft Access forms based on a SQL query are migrated to Oracle Application Express reports.

After you update the forms, select the ones you want to include in the migration.

To review retrieved forms:

1. From the project page, click Forms.

   The Forms page appears, showing the status of the objects ready for migration.

   
   Description of the illustration acmg_frm_pg.gif
   
   

   For each Microsoft Access form, the Forms page shows the following information, if available:

   • Source type:

     • Table

     • Query - The Oracle view that was migrated from the Microsoft Access query.

     • SQL Query - The original Microsoft Access SQL query that the Microsoft Access form is based on. Note that this query has not been parsed by the Oracle Migration Workbench. Therefore, you might must edit it to make it valid Oracle SQL syntax.

     • Nothing - The form has no underlying source type.

   • Source name - The Oracle table or view name if the source type is a table or query.

   • Status - Form status as Valid or Invalid. The source of the form must have a status of Valid before you can select it for migration.

     A form's status is based on two factors: status of its underlying source object and inclusion of the source object in the migration. Specifically, a form has a status of valid if either one of these situations exists:

     • Its Source Type object (table, query, or SQL query) is valid, and it has been included in the migration. Its check box is enabled and can be selected.

     • Its Source type object has a status of valid, but the source object was not included in the migration. Its check box is disabled.

     A form has a status of invalid if either one of these situations exists:

     • No Source Type is listed. Its check box is disabled.

     • Its Source Type object (table, query, or SQL query) is invalid. Its check box is disabled.

   • Startup form - Identifies the form that displays when you open your Microsoft Access database.

   • Parent form - Indicates the form/subform relationship that existed in your Microsoft Access database. For example, the CallListSub form shows Contacts as its Parent Form.

   • Migrate to: Form, Tabular Form, or Report and Form - The select list appears if the source type is a valid table.

2. To run a bulk process that attempts to compile all invalid SQL queries, click Attempt to compile invalid SQL queries.

   Using this option can validate some SQL queries that show a status of invalid. Note that SQL queries from Microsoft Access forms are not loaded into the Oracle Migration Workbench, and are therefore not parsed.

3. To edit a SQL query:

   1. On the Forms page, click the SQL Query you want to edit.

   2. Click Validate to find the invalid part of the SQL query.

   3. Click Edit.

   4. Update the query and validate it.

   5. When it is validated, click the project name breadcrumb.

   6. To include the validated query, click Forms on the project page to go to the Forms page. Then select the newly validated query in the left column and click Apply Changes.

4. To edit a query:

   1. On the Forms page, click Query for the form you want to edit.

   2. Click Compile to find the invalid part of the query.

   3. Click Access Query to review the initial query and compare it to the converted query.

   4. Click Edit.

   5. Update the query and recompile it.

   6. When it is validated, click the Queries breadcrumb.

   7. To include this validated query, select it in the left column on the Queries page and click Apply Changes.

5. To review details about a form, click the link in the Access Form column.

6. To include forms in the migration, select them in the left column.

7. Click Apply Changes to save your selections.

Reviewing Retrieved Reports

Next, review the reports retrieved from the Microsoft Access export. Application Migration identifies invalid reports and lists additional information, such as the report's source type and source name.

After you update the reports, select the ones you want to include in the migration. To include a report, the source of the report must have a status of Valid.

To review retrieved reports:

1. From the project page, click Reports.

   The Reports page appears, showing the status of the objects ready for migration.

   
   Description of the illustration acmg_rpt_pg.gif
   
   

   For each Microsoft Access report, the Reports page shows the following information, if available:

   • Source type:

     • Table

     • Query - The Oracle view that was migrated from the Microsoft Access query.

     • SQL Query - The original Microsoft Access SQL query that the Microsoft Access form is based on. Note that this query has not been parsed by the Oracle Migration Workbench. Therefore, you might must edit it to make it valid Oracle SQL syntax.

     • Nothing - The report has no underlying source type.

   • Source name

   • Status of the report: Valid or Invalid. The source of the report must have a status of Valid before you can select it for migration.

     A report's status is based on two factors: status of its underlying source object and inclusion of the source object in the migration. Specifically, a report has a status of valid if either one of these situations exists:

     • Its Source Type object (table, query, or SQL query) is valid, and it has been included in the migration. Its check box is enabled and can be selected.

     • Its Source type object has a status of valid, but the source object was not included in the migration. Its check box is disabled.

     A report has a status of invalid if either one of these situations exists:

     • No Source Type is listed. Its check box is disabled.

     • Its Source Type object (table, query, or SQL query) is invalid. Its check box is disabled.

2. To run a bulk process that attempts to compile all invalid SQL queries, click Attempt to compile invalid SQL queries.

   Using this option can validate some SQL queries that show a status of invalid. Note that SQL queries from Microsoft Access forms are not loaded into the Oracle Migration Workbench and are therefore not parsed.

3. To edit a SQL query:

   1. On the Reports page, click the SQL Query link you want to edit.

   2. Click Validate to find the invalid part of the SQL query.

   3. Click Edit.

   4. Update the query and validate it.

   5. When it is validated, click the project name breadcrumb.

   6. To include the validated query, click Reports on the project page to go to the Reports page. Then select the newly validated SQL query in the left column and click Apply Changes.

4. To edit a query:

   1. On the Reports page, click Query for the report you want to edit.

   2. Click Compile to find the invalid part of the query.

   3. Click Access Query to review the initial query and compare it to the converted query.

   4. Click Edit.

   5. Update the query and recompile it.

   6. When it is validated, click the Queries breadcrumb.

   7. To include this validated query, select it in the left column on the Queries page and click Apply Changes.

5. To review details about a report, click the link in the Access Report column.

6. To include reports in the migration, select them in the left column.

7. Click Apply Changes to save your selections.

Reviewing Database, Module, and Pages Information

From the project page, you can drill down to see information about the database, modules, and pages for the migration project.

• Database - Displays summary information about the Microsoft Access database, including the full path and size of the .mdb file.

• Modules - Displays the Visual Basic Code, enabling you to extract embedded SQL statements for you to use or edit in your Oracle Application Express application.

• Pages - Displays information for reference purposes.