Subj : System check ???
To   : Gerald Miller
From : Jasen Betts
Date : Mon Oct 28 2002 08:02 pm

Hi Gerald.

27-Oct-02 10:09:54, Gerald Miller wrote to Jasen Betts


 GM> Hello Jasen,

 JB>> what 4dos version are you targeting? the current version supports
 JB>> different formats in %@makedate, but not in %@date (strange omission)

 GM> I'm not targeting any particular 4dos version specifically, but the
 GM> version
 GM> that I'm currently using is 6.02B.  Hopefully, the newer versions will
 GM> still
 GM> perform the batch.  I have to wonder if JPSoft purposely omitted support
 GM> for
 GM> different formats in %@date...  To maintain backward compatibility??

They didn't break too much when they changed fron 6 to 7 :)

 GM>>> I'm not familiar with the ISO format....

 JB>>  echo
 JB>> %@replace[2,d,%@replace[20,yy,%@replace[1,m,%@makedate[14936,4]]]]
 JB>>                                                             /\
 JB>> :)                                                          ||

 GM> In your previous message, you had omitted the ",4" at the end, but it
 GM> still
 GM> worked on my system. (???) Help me out and tell me how you achieved the
 GM> numbers
 GM> "14936,4" and what is their significance

 14963 is 22nd of November 2020

That way I can replace "20" with "YY", "1" with "M" and "2" with "D"

the ",4" makes it use ISO format here (needs version 7 of 4dos)

Here it says comes out of makedate as 2020-11-22 which gets translated
to YYYY-MM-DD

[squiched by me]

 GM> PATH\PROGRAM TO RUN               ³AFTER³        ³        ³DAYS ³
 GM>                                   ³ DAYS³LAST RUN³NEXT RUN³ LEFT³ASK

Why all the new fields? - aren't program, After-days, last-run and ask
enough ? is it so you can add some new scheduling rules?

  -=> Bye <=-

---
 * Origin: Chicken Little was right. (3:640/531.42)

.