Here are some time-saving suggestions for a smoother conversion from MS-DOS AREV to AREV32 on Windows. This information is based on the 8.0.8 version of OpenInsight.
"XXX" should be replaced with your desired OpenInsight/AREV32 application name.
OpenInsight/AREV32 Install
-
Install OpenInsight version 8.0.8 or later
-
Make sure that no parts of your OI pathname exceed 8 characters in length (i.e RevSoft\Openinsight 8.0.8 may cause trouble with some DOS-based utilities)
-
Install and configure network services and drivers on OI server
-
Create the XXX application in OpenInsight, using the same name as the old AREV account, if possible
-
If running on a network, set the CTO record in SYSENV to "." so that OpenEngine Server is running locally. It's much easier to recover from AREV32 aborts (which can stall the OpenEngine server) when it is running locally than on the database server
AREV (DOS) Preparations
-
Copy the entire DOS application and database to the same server that will be used for OI/AREV32 before executing the following steps
-
Delete all AREV Volume pointers in VOC and avoid re-implementing under OI if possible
-
Remove all MFSs except for SI.MFS
-
Remove all XREF and Relational indexes (Btree indexes are OK even on AREV versions prior to 3.0).
-
Remove or rename any tables that might conflict with OI standards (e.g. SYSLISTS)
Before Re-running an AREV32 Conversion
-
Erase the contents of all target application directories
-
Delete XXX_AREV32_CONVERSION_ERRORS from Sysenv table in OI
-
Remove all attached application tables via database manager
-
If you get VOC file errors on a re-conversion, delete and re-create your target application in OpenInsight from scratch.
Conversion
-
Refer to current AREV32 documentation for complete details
-
Login OI to XXX application
-
from System Monitor, run "EXEC AREV_TO_AREV32"
-
Click "Load Info"
-
Specify ALL directories to be converted in the exact same order as the old AREV logon attach sequence
-
set Options;
-
REBUILD INDEXES: Y
-
CHANGE DOTS TO UNDERSCORES: Y
-
RECOMPILE: N
-
COPY TABLE: Y
-
Click "Convert App"
-
Press ENTER key on "Invalid Table Handles"
-
Wait several hours for conversion to run
Post-Conversion Configuration
-
Login OI to XXX application
-
If your target application has a new name, copy the old application name to the new application name in the SYSENV file or AREV32 won't see the new application.
-
Copy your old application name to "SYSPROG" in SYSENV if it doesn't already exist.
-
Copy SYSMENUS STARTUP over MAIN to get the correct menu in AREV Sysprog (bug fix).
-
Open OI Database Manager and attach all converted volumes in the correct order
-
Review contents of XXX_AREV32_CONVERSION_ERRORS in sysenv to remedy, ignore and/or re-run the conversion
-
Set File/Application Properties/Entry Point to AREV32_CHILD_FORM in Open Insight,
-
Always run your application via OpenInsight. Add the /DV=1 switch to the shortcut to prevent the CHILD_FORM from starting automatically, then use the "Launch App" button to run your AREV32 XXX application
-
You can add MFS routines in OI or in AREV32, however you must (re)attach your MFS'd tables in AREV32 after cataloging the programs or they will be ignored.
-
rebuild all Xref and REL indexes
-
define all available print queues using AREV32 Printer Environment window. Make sure that all station network paths match port-forwarded printer definitions created on OI database server.
-
Test OIPI access on all client stations to register COM components
-
Replace all R/Basic viewer references with OIPI.
See also Revelation Software's Quick Start guide and AREV32 Tutorial.
