In a message of , Richard Webb (1:283/525.5) writes:

 RW> JN>    Event All  23:59 23:59      F            E1=70  E2=30  E3=30

 RW>RJT> I do for some things,  like the midnight maintenance events...

 RW>Right, but the date rolled over, and binkley recreates .day and adjust 
 RW>.scd, I believe.  You've rolled over the date.  Therefore, it knows 
 RW>nothing about did or *didn't* run 23:59 event. 

Long ago I also had a 23:59 forced event for midnight maintenance, and my
accept a call event ended at 23:50 (Bink was told to not answer the phone
after 23:50) but I still on occasion missed the 23:59 forced event. 

 RW>Things are working properly.  It didn't run because at the time the freq 
 RW>finished, it was already the next day, probably 00:whatever.  So, binkley 
 RW>ran the first event of the day, and went on about its business.  

Which is correct. It should be noted that once a session starts, Bink will
ignore the event files (.evt, .scd and .day) until the session ends. It
will however act upon any session controls set up in the .cfg file and thus
a freq can easily go over the end of an event and maybe the entire duration
of the next event if the freq takes long enough and the event is short
enough.

 RW>If you don't want your 23:59 event missed, move your other event to 23:59 
 RW>for end time,

I did not do this, and the above comment also indicates that a call can
still exceed the 23:59 limit.

 RW>and start your forced maint event at 00:00, and it'll run no matter 
 RW>what.  

But the forced maintenance event at 00:00 is also my solution to the
problem. A freq lasting an hour starting at 23:50 will continue to 00:50
and the forced event will run at that point in time. The same is also true
if a call is answered between 23:59 and 00:00, it will also continue into
the next day, and the forced event runs when that call finishes.

 RW>Regards,

Refards,

 RW>Richard
 
       Richard.


--- Msged/Q 1.60