Hi! Richard,   
      
   In a message to All you wrote:   
      
    RW> One thing I've always wanted to implement was a bit of a   
    RW> history section, keyed by date.  These go out on Sunday   
    RW> mornings, of course.   
      
   Uh, huh.   
      
    RW> This batch would run at midnight utc on Sunday of course adn prepare   
    RW> the history information, compiling into it a file that the weekly    
    RW> email generator code would find.   
      
   Okay, I want to look at your system... no scripting at this point...   
      
   The daily files consist of some sort of activity logs?  The weeklies consist   
   of a compilation for the previous week?   
      
   I would be looking at a system something similar to...   
      
   -----8<-----C-U-T--H-E-R-E----->8-----   
   remark: YYYYMMDD.txt is the daily transaction/logging file   
   remark: the weekly file weekMMYY.txt is built on-the-fly after each day's   
   logging   
      
   DAILY_LOOP   
     LOGGING_LOOP   
       YYYYMMDD.txt = [YYYYMMDD.txt + (new activity log entry)]   
     END LOGGING_LOOP   
     weekMMYY.txt = [weekMMYY.txt + YYYYMMDD.txt]   
     archive YYYYMMDD.txt   
     kill YYYYMMDD.txt   
   END DAILY_LOOP   
      
   WEEKLY_JOB   
     post weekMMYY.txt in email   
     archive weekMMYY.txt   
     kill weekMMYY.txt   
   END WEEKLY_JOB   
   -----8<-----C-U-T--H-E-R-E----->8-----   
      
   This system probably varies a little from what you intended.  Can you explain   
   what I might be missing?   
      
    RW> So, taking this Sunday's for example, the batch would look   
    RW> in a defined directory for files named 0115.txt; 0116.txt; 0117 ...   
    RW> etc.   
      
   Ermm... shouldn't that be 0108.txt; 0109.txt; 0110.txt...  :)   
      
   (With the system I propose, those files won't be necessary.  The weekly file   
   would be built-up during the week's daily operations.  They would still be   
   available in the relevant archive if something screws up, somewhere.)   
      
   Question.  What happens Sunday 5 February, with the 30th & 31st of January's   
   logging?  Do they get caught up in "week0212.txt"?   
      
   Cheers,   
   Paul.   
      
   ---    
    * Origin: !WARNING(205): Power not on. Press any key to continue. (3:640/384)