long variable error... a fix needed for 5.5.

[John Esak]

OOPS! I forgot something _very_ important... the very thing I was talking
about... :-)  There needs to be a "global" in the declaration below as in:

     then: declare GLOBAL date(8,mdy/,g)

Sorry...
JE


>
> I do, though, and this is _very_ important, feel that there should be NO
> need to declare a long variable on an automatic table just to get
> it to pass
> globally among tables. In other words, we MUST never lose the
> ability to do
> this on a -v table:
>
>           if: date ne ""
>         then: goto sel
>           if:
>         then: declare date(8,mdy/,g)
>           if:
>         then: input popup date "Draw this report for what date? "
>           if: @sk eq "BRKY"
>         then: exit
>           if: date eq ""
>         then: goto askD
>    sel    if: 2 eq date
>         then: select
>           if:
>         then: end
>
>
> I use this kind of process hundreds of time a day/month/year...
> It is seldom
> that I rely on AUTOMATIC tables for anything these days... mostly
> legacy...
> now that the above is possible... AND I can show that variable
> 'date' on the
> report format by stuffing it into a 2 character global variable there.
>
> So, as long as this doesn't go away... I'm for not having the
> long variables
> carry the multiple copies.
>
> John Esak
>
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list