Why?

Brian K. White brian at aljex.com
Tue Jun 29 16:26:28 PDT 2004


----- Original Message ----- 
From: "George Simon" <george at worldest.com>
To: "Kenneth Brody" <kenbrody at bestweb.net>
Cc: "'Filepro-List'" <filepro-list at seaslug.org>
Sent: Tuesday, June 29, 2004 3:17 PM
Subject: RE: Why?


> All dummy fields (gu, gv, gw, lct, etc.) are all defined as lowup.
>
> I guess my question is "Why does code that works with d/rclerk, foes not
> work with d/rreport?"

Auto processing? Commands or system fields or other features that work
differently (on purpose) between clerk & report? Could be any of a zillion
things that no one but you is in a position to diagnose.
There may in fact be a filepro problem, but so far you have not shown it
yet.

I know if I punched that code in it wouldn't fail for me either.
Ask me how I know :)

Since "it worked for me" then there is something else besides what you have
shown so far, because I adhered to everything you said so far, which only
leaves about a million other things that could still be different between my
test and yours.
hmm, well, one thing that's different is I used 5.0.13 sco unix.

here is my exact prc.test in it's entirety, except I edited out the site
password:
-----begin-----
top::gu(2,lowup) = "gu" ; gv(2,lowup) = "gv" ; gw(2,lowup) = "gw":
::gx(2,lowup) = "gx" ; gy(2,lowup) = "gy" ; ma(2,lowup) = "ma":
::mb(2,lowup) = "mb" ; me(2,lowup) = "me" ; mf(2,lowup) = "mf":
::ky = "|":
::lct = ""{gu{ky{gv{ky{gw{ky{gx{ky{gy{ky{ma{ky{mb{ky{me{ky{mf:
::msgbox lct:
::lct = xlate(lct,"|"," "):
::msgbox lct:
::end:
@keyt:' written so that the same code can be run in both clerk & report:goto
top:
::declare lct(30,lowup):
-----end-----

And here are the commands I used to test it:
rreport test -fp test -y NoAuto
rclerk test -z test -y NoAuto

And it worked perfect both times.

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani



More information about the Filepro-list mailing list