{{tag>category:"None Specified" author:"Jeff Bowker" author:"Donald Bakke" author:"Kurt Baker"}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== Migrating to OI from RevG (None Specified) ====
=== At 23 NOV 1999 10:45:01AM Jeff Bowker wrote: ===
 
 
<QUOTE>
I am migrating from RevG to OI.  I need to bring over my data from RevG to OI without bringing over my dictionaries, which are already in OI.  To do this it has been suggested that I use PORTER in RevG to create an ASCII file and then use the IMPORT ASCII file in OI.  My problem is this, should I create an ASCII file with variable or fixed length fields in PORTER.   If I go with fixed, in OI it prompts me to enter lengths for each field, in the case of multi-value fields, my length would change dramatically.  Any suggestions???
</QUOTE>
----

=== At 23 NOV 1999 11:40AM Donald Bakke wrote:  ===

<QUOTE>Jeff,



If you can manage variable length fields then this would be the most ideal. However, unless you are writing your own import process I don't know how you will manage the multi-valued fields.



We generally use AREV to attach the Rev/G tables and copy the records to an AREV/OI table. Works very well.



dbakke@srpcs.com

[url=http://www.srpcs.com]SRP Computer Solutions[/url]

[img]http://www.srpcs.com/srpicon1.gif[/img]

</QUOTE>

----

=== At 23 NOV 1999 12:29PM Kurt Baker wrote:  ===

<QUOTE>The easiest way to get from RevG to OI is via Arev - do you have a copy handy?



In Arev there is an IMPORT/FILE option that will take a RevG file and convert it directly into an Arev/OI file format. This IMPORT/FILE process asks you where your RevG files reside and then allows you to change the file names or account (you'll want to get rid of files/accounts with dots in them).  The utility also lets you convert multiple files at once.  After running the IMPORT/FILE option you then can run the DICTCOMPILE or COMPILEDICT function to recompile your dictionaries into the AREV/OI dictionaries.  After the Dict and Data files are converted - you can then run the program that removes dots from dictionary files (see source code for this program is in the knowledgebase - under the document - Extending Arev applications).  By taking these three pretty easy steps, you can bypass all the headaches of dumping the data out, recreating the files & dicts - etc.







I am migrating from RevG to OI. I need to bring over my data from RevG to OI without bringing over my dictionaries, which are already in OI. To do this it has been suggested that I use PORTER in RevG to create an ASCII file and then use the IMPORT ASCII file in OI. My problem is this, should I create an ASCII file with variable or fixed length fields in PORTER. If I go with fixed, in OI it prompts me to enter lengths for each field, in the case of multi-value fields, my length would change dramatically. Any suggestions???

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=17C43B240F73FB5B8525683200568521|View this thread on the Works forum...]]