Long variable prob with break processing still

[John Esak]

Ah, okay... guess I got the other message late... or rather before we talked
in the room...
JE

> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of GCC
> Consulting
> Sent: Wednesday, April 06, 2005 11:35 AM
> To: rkreiss at gccconsulting.net; 'Shane Gray'; 'filePro List'
> Subject: RE: Long variable prob with break processing still
>
>
> Top post,
>
> Retest this problem after talking with John.  He pointed out that
> the method I
> used was incorrect.
>
> I had set the values individually and it worked.
>
> However, when I did as you did or even used another dummy field
> to pass the lone
> variable's value, aa was always empty at the break.
>
> @wgt :if aa = ""
>     then: aa = "EMPTY"
>
> This is the result when the report ran.
>
>    -----------------------------------------┐
>    │ Test AA is  EMPTY                           │
>    │ Declared Value is  Value of Test LONG       │
>    L------------------------ Press  Enter     -
> Richard Kreiss
> GCC Consulting
>
>
> > -----Original Message-----
> > From: filepro-list-bounces at lists.celestial.com
> > [mailto:filepro-list-bounces at lists.celestial.com] On Behalf
> > Of GCC Consulting
> > Sent: Wednesday, April 06, 2005 10:54 AM
> > To: 'Shane Gray'; 'filePro List'
> > Subject: RE: Long variable prob with break processing still
> >
> >
> >
> > > -----Original Message-----
> > > From: filepro-list-bounces at lists.celestial.com
> > > [mailto:filepro-list-bounces at lists.celestial.com] On Behalf
> > Of Shane
> > > Gray
> > > Sent: Tuesday, April 05, 2005 9:54 PM
> > > To: filePro List
> > > Subject: Long variable prob with break processing still
> > >
> > >
> > > Could someone verify if this is a problem or just me
> > thinking it was
> > > supposed to be fixed.
> > >
> > > filepro v5.0.14 SCO.  d/rreport.
> > >
> > > Assigning a long variable to a normal dummy during main processing
> > > forces the dummy to lose its value in break processing.
> > See following
> > > code sample.
> > >
> > >   1  -------   -   -   -   -   -   -   -   -   -   -   -
> > >        . If:
> > >        Then: declare testlong(5,*,g)
> > >   2  -------   -   -   -   -   -   -   -   -   -   -   -
> > >        . If:
> > >        Then: aa(5,*,g)="abcde"
> > >   3  -------   -   -   -   -   -   -   -   -   -   -   -
> > >        . If: 'this breaks it, only declare global works
> > >        Then: testlong=aa; aa=testlong
> > >   4  -------   -   -   -   -   -   -   -   -   -   -   -
> > >        . If:
> > >        Then: end
> > >   5  -------   -   -   -   -   -   -   -   -   -   -   -
> > > @wgt   . If: '
> > >        Then: '
> > >   6  -------   -   -   -   -   -   -   -   -   -   -   -
> > >        . If:
> > >        Then: msgbox "aa="&aa&" testlong="&testlong; end
> > >
> > > It doesn't matter what combination of ,g on the long variable and
> > > dummy variable is used.
> > >
> > > If it's not just me I will report to fpsupport.
> > >
> > > Thanks.
> > >
> > >  Shane Gray
> > >  Senior Software Engineer
> >
> > Shane,
> >
> > I test this using 1.0.13 ODBC and the long variable held its
> > value at @wgt.
> >
> > Just a suggestion, have e you used the debugger to test the
> > values after being set?
> >
> > Checked the value when @wgt is executed prior to the msgbox
> > being displayed?
> >
> > You might also use a \n between the values: msgbox
> > "aa="&aa&"\n testlong="&testlong Just to make the display clearer.
> >
> > Richard Kreiss
> > GCC Consulting
> >
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
> >
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list