Advice for AREV32 Users [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== Advice for AREV32 Users =====

AREV32 users who wish to run AREV64 on their new OpenInsight 10 systems should note that the OI10 VOC items may be different from the OI9 VOC, and thus you should **not** replace an OI10 VOC with an OI9 VOC.  Instead, you should create a new VOC on the OI10 system, and then copy any custom OI9 items into this OI10 VOC.

==== Creating the OI10 VOC ====

When creating the application in OI10, there are additional options for AREV users available on the "Advanced" tab of the application creation dialog.  You should specify that you wish the OI10 application to have its own VOC table, at least; if you had multiple AREV applications, each with their own AREV tables, then you might also choose to have the OI10 application have its own set of AREV tables to keep your applications "isolated."  The application-specific tables that will be created include VOC, DICT.VOC, BATCHUPDATE, CAPTURED, HELP, IMPORTEXPORT, LISTS, MACROS, MENUS, MESSAGES, OBJECT, POPUPS, REPORTS, SOURCE, SYSALIASES, SYSVIEWS, SYSEMBEDDED, SYSRELATIONS, and WINDOWS.


{{:oi10:converter_quick_start:create_voc.png?400|}}

In the "Location" textbox, either enter, or browse to, the folder where the unique VOC or full set of AREV system tables should be created.  Much as you might have a folder called MYAPP_DATA in your OpenInsight 10 directory to hold the data files for your MYAPP application, here you might specify something like C:\REVSOFT\OI10\MYAPP_AREV_FILES.
==== Updating the OI10 VOC ====

After the conversion process has completed, you must now manually attach the OI9 VOC as an "alias", and copy in any missing VOC items to OI10.

=== Attaching the OI9 VOC ===

To alias the OI9 VOC, you can use the Database Panel.

{{:oi10:converter_quick_start:database_panel.png?400|}}

If the Database Panel is not currently enabled, in the IDE of your OI10 application, go to the View menu, select Tool Panels, and then select Database.

{{:oi10:converter_quick_start:file_view_panels.png?400|}}

From the Database Panel, click on the Alias button.

{{:oi10:converter_quick_start:alias_button.png?400|}}

Next, select "Directories" and then navigate to the folder where your OI9 VOC is located.

{{:oi10:converter_quick_start:alias_table_1.png?400|}}

Select your OI9 VOC file, and give it an alias name (such as TEMP_VOC).

{{:oi10:converter_quick_start:alias_table_2.png?400|}}

If you are comfortable using the System Monitor, you could alternatively issue something like the following command:

   ALIAS_TABLE "D:\REVSOFT\OI9.4.2\AREV_DIR","SYSPROG","VOC","TEMP_VOC"

=== Copying the OI9 VOC ===

Now that the OI9 VOC is available to your OI10 application, you must copy in the OI9 VOC items **without** overwriting the existing OI10 items.  You can invoke the COPY_ROWS dialog by typing COPY_ROW to the TCL line in your OI10 IDE.

{{:oi10:converter_quick_start:copy_row_1.png?400|}}

Enter the name of the aliased VOC table (TEMP_VOC in this example) as the source, VOC as the destination, and an asterisk ("*") as the name in both the source row and destination row textboxes.  Make sure the "Prevent Overwrite" radio button is selected, and then press "OK".  

{{:oi10:converter_quick_start:copy_row_2.png?400|}}


This should copy any missing VOC items from your AREV32 to AREV64 system.

If you are comfortable using the System Monitor, you could alternatively issue the command:

   COPY_ROW TEMP_VOC,*,VOC,*,0

=== Exiting OI ===

After the VOC items have been copied, you should exit your OI10 system - you will receive a warning that the database has changed, but you do //not// want to save the change (since you will no longer require access to the OI9 VOC).

{{:oi10:converter_quick_start:save_dbt.png?400|}}