I have been attempting to use either one to export my RevG database information. My issue is that everytime I use either one my RevG says V? not on file. Now, I have both files(porter and pdisk) under the same directory as the executable. When I start up my app, I can not copy (Result: 0 records copied), attach, or catalog(Result: File name?), either one of these files. This is probably a real simple issue, but it has been bugging me for hours. I do have $pdisk and $porter as well. Does either one of these files get listed when you simply put the file under the directory and run the RevG program?
Any help is appreciate.
Is that the error message? V? is not on file? The error messages normally mean something so their complete accurate text is useful.
The Sprezzatura Group
World Leaders in all things RevSoft
You are correct. Here it is:
:BASIC DOS C:\UNIWAY99\$PORTER
$V15 is not on file.
Whether it is PDISK or PORTER I get the same error message. Both of these commands are not listed under the VOC file; however, I do have a system diskette that has the command, BASIC, under the VOC file. I tried copying it using Qfile, but it said 0 records copied.
There's your problem. You are using a runtime version of the software which is not licensed for development and so cannot compile programs.
The Sprezzatura Group
World Leaders in all things RevSoft
As an aside if you try RUN VERBS PORTER does it say that $PORTER is not on file? Just wondering if the original developer had already compiled it.
The Sprezzatura Group
World Leaders in all things RevSoft
That is exactly what it says. I do have the System diskettes - Couldn't I run/compile the Porter or PDISK program from that diskette/RevG system?
Well it depends… is there anything that suggests your copy is a development version not a runtime?
World Leaders in all things RevSoft
Is there a $PORTER on the diskette? If so RUN DOS A:\PORTER from TCL would do it.
World Leaders in all things RevSoft
Yeah, I have a $Porter file.This is what happens when I run that command.
:RUN DOS C:\UNIWAY99\PORTER DOS,123
:
I thought it was supposed to give me a series of questions.
OK well looking at the PORTER source here (which hasn't changed for nigh on 20 years) it should be asking you for the name of the file to convert at this point. Someone may have modified your Porter routine, sorry.
The Sprezzatura Group
World Leaders in all things RevSoft
I just can't catch a break. Here is what happened when I attempted to compile the both Porter and pdisk:
:COMPILE DOS $PORTER
'$PORTER'
'$PORTER' Line 1 B102 Bad statement.
*
'$PORTER' Line 2 B102 Bad statement.
'$PORTER' Line 2 B102 Bad statement.
'$PORTER' Line 2 B123 Unmatched "NEXT", "REPEAT" or "END CASE";
'$PORTER' Line 2 B100 Compilation aborted; No object code produced.
:COMPILE DOS $PDISK
'$PDISK'
'$PDISK' Line 1 B102 Bad statement.
**
'$PDISK' Line 2 B100 Compilation aborted; No object code produced.
:
I think my best bet is to create a R/Basic program to export the database information.
The implication there is that PORTER is now in DOS format for some reason and needs to be reconverted to Rev G format before it will compile.
World Leaders in all things RevSoft
I might be confused…
"$PORTER" is the compiled version of "PORTER". You can not compile a compiled program.
Can you edit the "$PORTER" program and actually see source code???
Good call Richard - we blame the bug that's going around!
World Leaders in all things RevSoft
I seem to recall that you could create a template record somewhere and PORTER would not go interactive???
COMPILE DOS $PORTER???
That would attempt to compile and Object record wouldn't it. I think what you need is an original REV-G PORTER source program .. or failing that, an original compiled object record ($PORTER). Put the source into a file (typically BP) and compile it .. COMPILE BP PORTER. You should not receive any errors. Then RUN BP PORTER from the TCL.
Don M
Okay, I had the source to a couple of versions of PORTER in my REV G system.
But it looks like it will use Dictionary records @XFER, @XFERIN and @XFEROUT (depending on the version) to automate import/exports. Maybe only for ASCII import/export, I didn't look that closely at the code.