21 Migrating Applications

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 through SQL Workshop, a component of Application Express. For more information about SQL Workshop, see the Oracle Application Express User's Guide or the Application Express online Help.

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

     User interface defaults are used by 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 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 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 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 Application Express: form (default), report and form, or tabular form.

Microsoft Access forms based on a query are migrated to Application Express forms. Microsoft Access forms based on a SQL query are migrated to 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 need to 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 need to 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 Application Express application.

• Pages - Displays information for reference purposes.