Anyone know if it's possible to access RevG tables from Arev 2.xx or 3.xx? If it is possible, would someone mind posting the commands…

Take care.

I have not had success reading data from RevG tables, but I have converted RevG data to ARev linear hash.

This method will convert the old RevG data to ARev (version 3.x):

1. Attach the volume of where your RevG table is located. Make sure that in your location definition that it specifies that it is a RevG (ROS) files.

2. Attach the specific table that you want to convert.

3. Create an ARev table.

4. Use the COPYROW command to copy the rows across.

5. Any dictionary items will have to be re-built. Do not try to copy those across.

From there you can LIST, COUNT, etc. Let us know if this is helpful.

[email protected]

SRP Computer Solutions

Within Arev, use Set Volume to specify the RevG volume as being Revelation G type. Attach the Volume (using the volume name given, not the dos path) and then Revelation will know to access files in Rev G format.

Both of the postings contain essentially the correct information. Before you do the actual conversion, I strongly suggest that you go into REV G and rename the dictionary part of the file. If you attach the file, the process will attempt to load the dictionary and (in version 2.12 and later) will attempt to recompile the dictionary elements. This will leave you in a mess if you try to re-attach the table within G-REV. Even worse, if there are things that AREV doesn't like ($INSERT CN,RDESIGN.COMMON, for example), you won't be able to get to the data at all either in REV-G or AREV. Therefore,

CREATE-FILE TEMP.CONVERT in G-REV

this will create a dictionary with only @ID and @CRT

COPY * TO:(TEMP.CONVERT

then in AREV, attach TEMP.CONVERT and make a new table out of it

Don Miller

C3 Inc.

The main problem is as Don sums up: the dictionaries. Not only does ARev attempt to recompile the dictionary items, but it will also convert the layout to the appropriate version of ARev. In addition, the DICT.MFS will choke on symbolics that have Rev G code or @variables (e.g. @CONV) that is not supported in ARev leaving you with a dictionary that cannot be attached.

Here is another kludge method to get around this(BE SURE TO BACKUP FIRST!):

Use the FILE IMPORT Function in the TOOLS IMPORT menu (runmenu IMPORT from TCL in any version).

First in Rev G first create temporary files to hold the dictionaries. For example create a file D_INVOICES for the INVOICES file, D_CUSTOMERS for CUSTOMER etc.

Then copy all the items from DICT INVOICES to D_INVOICES, DICT CUSTOMERS TO D_CUSTOMERS etc.

Then CLEAR-FILE DICT INVOICES etc.

Next go into ARev and from TCL RUNMENU IMPORT. Pick FILE and fill in the blanks, be sure to include the D_filename you have created above. ARev will even to the NAMEVOLUME for the target directory if you haven't done so before.

Log out of ARev, Log back in. ATTACH the target directory from above.

Now for each D_file, copy * to:(dict file. Example: COPY D_INVOICES TO:(DICT INVOICES. Note any error messages (usually something to do with Protect Spec module) and the item names. Edit these items and correct any unsupported RBasic code.

Copy the corrected items to the appropriate dictionary. If you use the (D)elete option on the initial copy, only the items in error will be left in the D_file, making life a little easier.

Using the FILE IMPORT function maybe easier than Don's method because you can use the F2 key to tag the source files and convert several files at once in a batch mode.

View this thread on the forum...