[gopherhockey]

I have done and still do a lot of stupid things in my life, but lying about something like this and wasting everyone's time (espeically the author's) is not one of them.

I set it up as per instructed and got the dates completely right the first time. WHat happened may remain a mystery - perhaps a combo of the OS and software/mysql etc. - who knows.

I hope nobody else runs into this "bug" or whatever it is. I recommend running in test mode first, just in case... if you don't and if you have more users than I do, be ready to delete lots of threads and messages etc.

Perhaps to pull anything constructive out of all this, a person could use the example code you posted earlier to check to be sure both dates are correctly reported... I notice in the installation document you have us run a test that returns one date/time combo. Would it be an advantage to run it in a way that reports both? Or is one written the first time and one written after the first day when the first run completes..?

Here is another though. WHen I initially ran it, I had set my estimated load to 3 instead of 30. Is it possible that on that midnight when I was all click-happy to see it run that I kicked off the thing twice in a row so quickly that one of the instances didn't read the last run time either at all or properly and maybe caused that strange behavior?

Probably not worth further speculation...