The server will automatically change through timezones (DST and non-DST) when it is programmed to. When you manually change the time - you are not changing the timezone, but the actual base time. Again, Unix timestamps are always taken as UTC, so timezone changes do not affect this.

Ahhhhh OK that makes PERFECT sense then :up:

Nope, like I said, it stores them as the unix timestamp. This is translated into a display time by vb, depending on your timezone settings. The unix timestamp always moves forwards, whatever your timezone does.

Yes I know but what I was saying is that VB stores the TIMESTAMPS as GMT-0 which is equal to UTC

Unix timestamps are always seconds since January 1 1970, 00:00 UTC. Anything other than that is not a Unix timestamp.

It will not mess up the post order cause the post still have an ID number assigned to them, so you may see a post before time was set back with a time stamp of 1:02AM and a post number of #500 and no one post till DST has taken affect and the next post is post #501 with a time stamp of 1:01AM, I have been running forums for the past 12 years and this has always been the case and it has not messed up a single time.

and time is set back at 2am not midnight, so at DST when the clock is at 1:59am then another minute goes by it will be 1:00am

Posts are not ordered by post-id but by timestamp.

IF that was the case then in my example post #501 would be rearranged with post #500 after DST went into affect. cause post #501 was at 1:01am and post #500 was at 1:02am.