Re: BUG in CONVERT command - or I can't tell the time

2002-04-22 Thread Dar Scott
On Monday, April 22, 2002, at 05:53 AM, Michael D Mays wrote: > When it is 12 midnight in Edinburgh (GMT) it is 6:00 PM the day > before here > in Dallas (CST) (no daylight savings time). I haven't been reading my mail well, Michael. When I read Ian's mail the first time I thought he was com

Re: BUG in CONVERT command - or I can't tell the time

2002-04-22 Thread Michael D Mays
When it is 12 midnight in Edinburgh (GMT) it is 6:00 PM the day before here in Dallas (CST) (no daylight savings time). And that is the way it should be. If a child was born at zero seconds, okay 1 second, in Edinburgh a year later in Dallas at 6:00:01 PM on Dec 31st she would be a year old. IMO,

Re: BUG in CONVERT command - or I can't tell the time

2002-04-22 Thread Shao Sean
> Put 21600 into xxx > Convert xxx to short time try instead: convert xxx to short system time ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution

Re: BUG in CONVERT command - or I can't tell the time

2002-04-21 Thread Dar Scott
On Sunday, April 21, 2002, at 08:18 PM, Michael D Mays wrote: > That is what the documentation says. 0 seconds is 12 midnight, Jan > 1, 1970 > GMT. I get 6:00 PM (I was sure 0 used to get an error for me, too, I'm not sure what's up with that.) Look at at the original time header in the mai

Re: BUG in CONVERT command - or I can't tell the time

2002-04-21 Thread Michael D Mays
That is what the documentation says. 0 seconds is 12 midnight, Jan 1, 1970 GMT. Or at least close to it. There are discrepancies with convert for zero(s) seconds and -1 seconds. -2 secs -> 23:59:59 -1 secs -> 12:00:00 mid GMT -0 secs -> 12:00:00 mid GMT zero secs -> 0 (the result = invalid

Re: BUG in CONVERT command - or I can't tell the time

2002-04-21 Thread Dar Scott
On Sunday, April 21, 2002, at 03:25 PM, Ian Summerfield wrote: > My code used to work when we were on GMT, so no doubt it has > something to > do with the engine ignoring time zone settings. Your email shows +100 in the (original) date field, so I assume OS X knows BST. Dar Scott _