***SPAM*** Re: odd lookup problem
Richard Kreiss
rkreiss at gccconsulting.net
Wed Nov 10 10:07:42 PST 2010
> -----Original Message-----
> From: Jeff Harrison [mailto:jeffaharrison at yahoo.com]
> Sent: Wednesday, November 10, 2010 12:57 PM
> To: rkreiss at gccconsulting.net
> Cc: Filepro-list at lists.celestial.com
> Subject: ***SPAM*** Re: odd lookup problem
>
> ----- Original Message ----
>
> > From: Richard Kreiss <rkreiss at gccconsulting.net>
> > To: Kenneth Brody <kenbrody at spamcop.net>; rkreiss at gccconsulting.net
> > Cc: Filepro-list at lists.celestial.com
> > Sent: Wed, November 10, 2010 11:36:19 AM
> > Subject: RE: odd lookup problem
> >
> > New problem:
> >
> > Doing a lookup in the auto processing table using lv=master_code&"99"
> > to display information from the sales journal in the current file.
> > The NOT sales line shows false when a record is present in the sales
> journal.
> >
> > When @keyW is pressed and this lookup is done from input processing,
> > the NOT sales is true.
> >
> > I removed the casting lv from the input process as a test but NOT
> > sales still showed as true in input processing.
> >
> > My question is, why would the lookup return the correct value in auto
> > processing but not in input processing.
> >
> > Richard
> >
>
> Richard, it is difficult to say exactly without seeing ALL of the code
that is
> being executed here, but keep in mind that when you press "W" for your
> @key processing, that causes automatic processing to run first. Auto
> processing is likely doing something to mess you up.
>
>
> Try this as a test: Go into your looked up record without any processing
(
> dclerk filename -s0 -y none -z none) and verify that the data is as you
expect.
> Then test your code in input processing without any automatic processing.
I
> suspect that it will work fine. You are probably changing the data in
auto
> processing.
>
> Good Luck.
>
> Jeff Harrison
> jeffaharrison at yahoo.com
> Author of JHExport and JHImport
As I have been using this record for a few days to test programming and have
the debugger on in the auto processing table when it hits the lookup, I know
that the data is not being changed.
I have not tested the code without the auto table running. I would need to
create a new file with just this code and use -z new_table -y !! for the
test.
Richard
More information about the Filepro-list
mailing list