ML>> hummm... looks like it would work to me? what about to you? i haven't
 ML>> looked into the code and would have to learn it before attempting to
 ML>> put this mod in... seems like it should be easy enough to do...

 ML>> so, what do you say? add a great enhancement to an already good util?

 GM> I've got the flu and I'm taking a few days off....

hope you get to feeling better...

 GM> If you don't want to enter 26th.btm into the data file twelve
 GM> times (much more accurate), then put it in once and call
 GM> 26th.btm everyday (with the following [_untried_] adjustments);
 GM> until dayboot can be revised.

understood... one of my main goals is to get /away from/ using flag files
and the sundry utils i currently use to determine whether or not to run a
certain routine on a certain day... the idea is to simplify...

the idea of putting 26th.btm in 12 times is ok until you end up with 10 or
15 of them to do like that... for operations on 10 seperate days of the
month, you end up with 120 entries...

[trim]

 GM> === Cut 26TH.BTM ===
 GM> ::  The following *_should_* create a zero byte flag file in
 GM> the same drive /
 GM> ::  directory (named 26TH.FLG) as the 26TH.BTM file
 GM>   set flagfile=%{at}path[%{at}search[%0]]%{at}upper[%{at}name[%0]].FLG
 GM>     iff %_day[%date] == 26 then
 GM> ::  or maybe the above line has to be "iff %{at}day[%_date] == 26
 GM> then" (both
 GM> ::  #_may_# yield the same results) - /play/ with it.

i've already played with this to some extent while i wrote my initial
message with those code snips... that's how i knew which ones to suggest to
use in this modification ;-)  %_date is the one to use...

)\/(ark