@td question

[John Esak]

At the risk of having a conversation with myself... :-)  I see that this
message I sent complaining that my messages are not getting to the list...
gets to the list. Go figure. :-)

I'm going to chalk this up to just really strange and forget about it. But
same machine, same mailer, same everything... not a cc, but that can't
matter. One gets there, one doesn't. It's the new "Black Hole Virus". :-)

JE


> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of John Esak
> Sent: Monday, August 15, 2005 10:04 PM
> To: Fplist (E-mail)
> Subject: FW: @td question
>
>
> Okay, what gives? I sent this message up to the list hours ago. I
> never see
> it... then I see Ken Broday answer almost exactly the same thing as if he
> has never seen it also. Happened with Bob today, happened with
> Ken... except
> that I never even saw this message appear on the list and it is clearly
> marked for delivery to the list as a cc. Where exactly are my
> messages going
> if not to the list??
>
> John
>
>
> -----Original Message-----
> From: John Esak [mailto:john at valar.com]
> Sent: Monday, August 15, 2005 7:41 PM
> To: beppler at comcast.net
> Cc: Fplist (E-mail)
> Subject: RE: @td question
>
>
>
> -----Original Message-----
> From: filepro-list-bounces at lists.celestial.com
> [mailto:filepro-list-bounces at lists.celestial.com]On Behalf Of
> beppler at comcast.net
> Sent: Monday, August 15, 2005 6:52 PM
> To: filepro-list at lists.celestial.com
> Subject: @td question
>
>
> My client came to me with this today. He is running SCO Unix 5.07 Filepro
> 5.0.14R4.
>
>   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
> settle . If:                                   .
>        Then: bi(6,allup)="050816"                  'Effective Entry Date
> Settl>
> 124  -------   -   -   -   -   -   --   -   -   -   -   -   -   -
>   -   -
> -   -   -   -   -
>        . If: bi co "/"
> .
>        Then: beep;beep;beep;errorbox "DATE IN WRONG FORMAT, RETRY MENU
> OPTION !>
> 125  -------   -   -   -   -   -   -   -   -   -   -   -   -   -
>  -   -   -
>        . If: 'to check if date is not in past
>  ;       .
>        Then:
> fx(8,mdy/)=mid(bi,"3","2"){"/"{mid(bi,"5","2"){"/"{mid(bi,"1","2").
> 126  -------   -   -   -   -   -   -   -   -   -   -   -   -   -
>  -   -   -
>        . If: fx lt @td                                            .
>        Then: beep;beep;beep;errorbox "Settlement Date in the PAST !";exit
>
> Line 126 returns true when it is false.
>
> But if I change @td to @TD it works. I major problem if all system fields
> must be in caps now with FP version 5.0.14R4. Is this true?
>
> Any ideas? Is this true with all system variables?
>
> Thanks
>
> Brandt Eppler
> Synergistic Systems, Inc.
>
> Hi Brandt,
>
> Well, I'm not going to address the @td/@TD thing you bring up. I
> think that
> is quite impossible. There is NO difference to filePro whether the case is
> upper or lower. That aside. Is there any reason why you are putting the 6
> year-month-day field into edit type ALLUP?  Why not do this:
>
>
>       if:
>     then: bi(6,ydm)="050816"
>       if: bi lt @td
>    thend: show "@Date is less than today's date...";  end
>       if:
>     then: show "@Date is not less than today's date...";  end
>
>
> John
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list