Form question

[Don Coleman]

Top posted for John:

John, Ken, Wally, JPR:

You were all correct.  I was calling the correct form with proper syntax
which is the behavior I was seeing in the debugger.  However, after calling
the output table there are different portions of the output process table
where I issue the form command depending on the amount of processing left to
go for a particular customer (this aspect is somewhat customized for certain
customers & customer groups).  Out of about a dozen different lines where
the form is utilized, there were 2 out of my view (somewhere between columns
80-120) where I was still calling the old form.  I hadn't taken the time to
F9 Goto to make sure I had caught them all and the 3 sample records I was
using for testing all fell under the logic of the missed form calls.  While
using the debugger I was quitting out of it as soon as I saw the correct
output table being called.  

Chalk it up to haste makes waste (wasted time) but somehow I feel a big
"DUH" is more appropriate.   

Thank you all for pointing me in the right direction!


Don Coleman
Donald G. Coleman, Consultant
402 Andrew Circle
Indiana, PA 15701
dcoleman at dgcreact.com
(724) 349-6302

> -----Original Message-----
> From: John Esak [mailto:john at valar.com]
> Sent: Friday, August 24, 2007 10:14 PM
> To: Don Coleman
> Cc: Filepro-List at Lists. Celestial. Com
> Subject: RE: Form question
> 
> 
> Try this...
> 
> Make a new prc table (which you say you did already... but go again).  Put
> on it...
> 
>        if:
>      then: end
> @keyT  if:
>      then: aa="fred"
>        if:
>      then: add all the stuff you need for your new form
>        if:
>      then: form "newformname";  end
> 
> Put the AA on your new form with *aa somewhere... and see if when you
> press
> the T key does the form contain "fred" on it.
> 
> I'm kind of leaning with Ken that you are calling the wrong form. This
> will
> prove it out two ways.
> 
> Good luck.
> 
> John
> 
> 
> > -----Original Message-----
> > From: filepro-list-bounces+john=valar.com at lists.celestial.com
> > [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com]On
> > Behalf Of Don Coleman
> > Sent: Friday, August 24, 2007 3:15 PM
> > To: filepro-list at lists.celestial.com
> > Subject: Form question
> >
> >
> > List:
> >
> > Pulling my hair out 'cause I know I'm missing something.  I have a
> "clerk
> > process which calls a form and prints it.  I need to add two
> > fields to this
> > form which is already in use.  So I copy the input table and the form to
> > their own unique files so as to not interfere with current
> > production while
> > I ensure the alignment and all are correct.  I am running both the input
> > table and the form from dclerk/dreport with debug and see the
> > correct input
> > table and correct form being called.  My only problem is the fields I
> > re-arranged on the new form are not in their new positions, they are
> still
> > in the old positions.  I also set the output to print to file and the
> new
> > fields are in the old positions as well.  I remember seeing this
> behavior
> > before but always found my mistake, usually I wasn't "calling" the
> correct
> > path to my revised output.  Everything looks good (except my new
> fields).
> >
> > Any suggestions.
> >
> > Don Coleman
> > Donald G. Coleman, Consultant
> > 402 Andrew Circle
> > Indiana, PA 15701
> > dcoleman at dgcreact.com
> > (724) 349-6302
> >
> >
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
>