This one has me stumped.

I have an instance of sugar 5.2k running as normal. Timezone is America/Chicago (why they don't use standard time zones is beyond me, that's why they exist...)

I set my meetings ranging through nov 6.

ALL meetings set past 12:00 am nov 7 are being written directly into the db an hour past the time.

I know this because i have reports i've created, that pull from the DB and convert all the times with the same offset. Also extensive testing to see what was happeneing.

I imagine some of you will blame this on George Bush, and honestly with the timezone thing that may well be.

If there is some internal mechanism of sugar to translate daylight savings time where can i kill it at?

There is absolutely something interfering with times set past nov 6.

Quite aggravating... any clue?