Loading ...
Sorry, an error occurred while loading the content.
 

Re: [Clip] date for Sunday

Expand Messages
  • hsavage
    ... Adrian, What does the 3D at each variable entry point represent? Without that the clip works. If it s necessary add it after the calculations are
    Message 1 of 4 , Nov 19, 2012
      On 11/19/2012 4:55 AM, Adrian Worsfold wrote:
      > Hello hsavage, Flo etc.
      >
      > The first two lines under loop transposed still produce a false result:
      >
      >
      > ^!Set %Date%=3D^?{Enter a date (yyyymmdd):}
      > ^!Set %DateNr%=3D^$GetDateToInt(^%Date%;yyyymmdd)$
      > :Loop
      > ^!Inc %DateNr%
      > ^!IfSame "Sun" "^$GetDateFromInt(^%DateNr%;ddd)$" Match
      > ^!Goto Loop
      > :Match
      > ^!Info Next Sunday: ^$GetDateFromInt(^%DateNr%;yyyymmdd)$
      >
      >
      > 20121119 Produces Next Sunday: 18991231 when it is 20121125

      Adrian,

      What does the '3D' at each variable entry point represent? Without that
      the clip works. If it's necessary add it after the calculations are
      finished.

      ···············································
      ¤. JD#...324 - ¤. SL...980 - 12.11.19~07.40.17

      . Newspaper Headline...
      . Farmer Bill Dies In House.

      EUR hrs EUR hsavage EUR pobox EUR com


      [Non-text portions of this message have been removed]
    • Axel Berger
      ... That s a quoted printable encoding for 7-bit mail transfer, that someone s reader has not decoded again. All these encodings begin with = , which is why
      Message 2 of 4 , Nov 19, 2012
        hsavage wrote:
        > What does the '3D' at each variable entry point represent?

        That's a "quoted printable" encoding for 7-bit mail transfer, that
        someone's reader has not decoded again. All these encodings begin with
        "=", which is why the "=" itself has to be encoded too, yielding the
        ubiquitous =3D.
      • hsavage
        ... Thank s Axel. -- ··············································· ¤. JD#...324 - ¤. SL...980 -
        Message 3 of 4 , Nov 19, 2012
          On 11/19/2012 10:36 AM, Axel Berger wrote:
          > hsavage wrote:
          >> What does the '3D' at each variable entry point represent?
          > That's a "quoted printable" encoding for 7-bit mail transfer, that
          > someone's reader has not decoded again. All these encodings begin with
          > "=", which is why the "=" itself has to be encoded too, yielding the
          > ubiquitous =3D.

          Thank's Axel.

          --
          ···············································
          ¤. JD#...324 - ¤. SL...980 - 12.11.19~08.31.58

          . Newspaper Headline...
          . Farmer Bill Dies In House.

          EUR hrs EUR hsavage EUR pobox EUR com



          [Non-text portions of this message have been removed]
        Your message has been successfully submitted and would be delivered to recipients shortly.