I live in the middle of the US (Minnesota), and everyone here uses MM/DD/YY. It sounds (and looks) better saying "October 6th, 2003" than "the 6th of October, 2003", so that's probably why MM/DD/YY is also used the most. Probably the best thing for FLSO to do is have a little notice that the date format is MM/DD/YY; it's impossible to flawlessly, programmatically allow both to be used (unless there's a flag or something, of course).

It only sounds better and looks better to you because you are used to it. But honestly, it doesn't make sense. The US is the only country that I know of that uses that date format - the rest of the world uses DD/MM/YY. I'm in the US but whenever I use dates I try to use the international format because it causes less confusion in the long run. Now I just need to get used to using the metric system. . .

I couldn't believe it when I heard it at first either... but yeah, VB's internal date functions are affected by the damn regional settings in m$'s OS.

ANYWAY, I think I have a fix for it (Pinger has yet to get back to me verifying the problem is solved).

As mentioned, IFSO1 users, you were warned about non-north american regional settings and I'll do it again I wrote and tested the software myself on said configuration, and anything else might possibly not work properly. I'd like to make it work for everyone as well as I can and I'm trying my best, but there still is always a chance that something may go wrong. ALWAYS back up your files! Hopefully I've fixed this bug for good and version 2 won't harm anyone's servers like version 1 can.

-- JoeBoomz
IONCROSS