-r variables

[RKreiss1]

This is more of a reminder for those of us who use -r command line variables
to pass information.

I have a routine which allow for the printing of up to twenty invoices and
packing slips which runs from a clerk process.  

The invoice program, if run directly from the menu not using this routine,
will prompt, with an input popup to print or exit.  When coming from the
"print All" routine this popup needs to be skipped.  

The command line passes a counter value ct(2,.0) using -rw as part of the
command line passed to system.  The invoice print program had

If: @pw gt "1"
Then: GOTO printit

This worked fine until the 10th invoice was set to print.  At this point the
input popup appeared for the next 11 invoices.  To get around the problem
the clerk would put a stapler on the <enter> key so she didn't have to sit
there and press <enter> each time.

The problem was mine, as some of you would point out.  To correct the
problem, I added the following:

If: pw(2,.0,g) = ""
Then: pm=@pw
If: @pw gt "1"
Then: GOTO printit

This solved the problem.  It appears that I needed to use and numeric field
to insure that this routine worked properly.

So, if you are passing values at the command line and for some reason your
program does not seem to be responding properly to the @p...,
Try using a temporary field or long variable with the proper edit applied.


Richard Kreiss
GCC Consulting
rkreiss at gccconsulting.net