Could anyone tell me if it is possible to access and report on (not update) revG tables from within AReV without corrupting the revG dictionaries?

Thanks

Bob Watson

You can use the import file tool for Rev G files which will convert the files and dictionaries to ARev format and access them that way.

(not quite sure this will work) Or you can use the above only on the dictionaries then do a:

SETVOLUME revg RTP59 c:\revgfilepath c:\converteddictionarypath

(lower case should be entered in as appropriate to your situation)

Then ATTACH revg

Thanks for your reply - what I would like to do is use arev as a reporting tool for REvG. So I need to attach live files. Does the mere act of attaching them corrupt the dictionaries or do I need to access the dictionaries before this will happen? Has anyone tried this before?

Bob Watson

I think this will work …

First, make sure that your REVG dicts have no errors.

Next - define a volume pointer to the location where your REV-G files are: DB-Admin-]Define..Give it a name: GREV-ROS or GREV-LNK, for example. There are 2 Rev-G filing systems..ROS files and LNK files. If you need both, then you'll have to make 2 entries. You should then be able to attach these volumes and use the tables.

Another possibility is to create valid AREV dictionaries and just then use these (LIST REVFILE USING AREVDICT …). This used to work ok in REV 2.x. I'm not sure if it's still ok in AREV 3.x (you may have to enable the dots option …)

Don Miller

C3 Inc.

Don

So you are saying that if I define a volume pointer and then attch the revg files, and don't access the dictionaries, I should be ok?

I like the "using table" option - that might mean I can use rlist etc..?

Thanks

Bob Watson

Don

Oh and what do you mean by enable the dots option - is there some provision to allow tables and dict rows to have dots in version 3 and above?

Bob Watson

I tested the following here before I posted..

In AREV 3.12

DB Admin-]Define..Volume Name: REVG Location C:\GREV\TEMP .. This was a temporary directory with about 25 files (LNK and ROS files). Ignored the Control files location. Attached the Volume pointer:

ATTACH REVG .. LIST INVOICE .. (It has a @CRT G-type element). Worked fine. LIST CUSTOMER .. Error Message @ID is invalid .. (probably due to a lack of data type) LIST CUSTOMER USING VOC worked fine. I copied the fields I needed from DICT.CUSTOMER into DICT.VOC and used the DICT utility to clean up what I needed. Worked fine..

My comment about the "Dots" option went back a while when I upgraded a copy of AREV 2.12 to AREV3 and then AREV3.12. I don't remember the details but I recall that there was an option about retaining dots in table and dictionary names.

HTH

Don Miller

C3 Inc.

Bob - REVG is RTP52. It will be possible to

(a) FROM AREV OSREAD the entire ROSmedia map,

(b) identify the file you want in DOS (ROS12345.LNK or ROS12345.0??)

© traverse each frame to remove records, or read a discrete record from the file, if you know the key values.

I *may* have some code lying about which will half do the job.

You could set up dictionary items for your REVG files in AREV's DICT.VOC to get the reports to work.

steve@state-of-the-art.com.au

Don

Thanks - I will experiment with the "using table" option - are you sure your revg files where still accessible after using rlist?

I appreciate the help

Bob Watson

Steve

Are you suggesting this method because it is not safe to set a volume pointer, attach the revg volume and read the rows directly?

Thanks

Bob Watson

They are different BFS's, so effectively, AREV code won't talk to *.LNK files (RTP52), in the same way it won't talk to MS Access database files.

Steve

And yet I can rbasic read from them with no problems????

Bob Watson

And yet I can rbasic read from them with no problems????

Bob Watson

Bobo,

I stand corrected - this feature was enabled in AREV 3.12 (possibly earlier?) but last time I tried to do this I was in AREV 2.x which lacked the feature. In AREV 3.12,

SETALIAS REVGVOLUME SYSPROG DATA VOC REVGVOC

will enable you to list the REVG file using AREV. You can use DICT.VOC to house standard dictionary items.

LIST REVGVOC

Steve

Steve

Yes - I've just been done the job as long as I don't attempt to access the reg dictionaries under any circumstances I was ok - I soon as I did the revg doctionaries were corrupted.

Thanks for the help (and Don)

Bob Watson

This works beautifully:

Create a directory or folder (eg DOS MD C:\RGDICT

From TCL:
SETVOLUME REVGDICTS RTP57 C:\RGDICT
RUNMENU IMPORT -] FILE
  Source File= pathtoRevGfiles
  Target File= REVGDICTS
Source files             New Names
account,DICT.filename    DICT.filename


ATTACH REVDICTS
DICTCOMPILE DICT filename

SETVOLUME REVGDATA RTP59 pathtoRevGfiles

ATTACH REVGDATA
ATTACH REVDICTS

Then you can do all the RLIST statements you want. The only thing you must make sure is that the REVG dict does not contain any unsupported RBasic code or @vars (such as @CONV) prior to running the Import or the import function will bomb.

Warren

That's a beautiful thing - I will use it thanks very much. Means I can use other ARev tools like the popup builder as well.

Thanks again

Bob Watson

Just be sure to always attach the converted dictionaries AFTER attaching the REVG volume.

Whoops ..

You're right. If AREV 3.X or 2.1x process REVG dicts, it will convert them. AREV 1.x and 2.0x don't. I guess I've almost always made AREV dicts for GREV files since upgrading to 2.1x that I forgot to mention it. Sorry if I gave you heartburn. The USING option does work however. Also, when you define the volume pointer to GREV, you can specify the location for your control files (which can be AREV dicts).

Don Miller

C3 Inc.

Don

Thanks for the help - i've got it all working due to help form this tread.

Bob Watson

View this thread on the forum...