> At a few of our customers' sites we are having a problem since the start of
> daylight savings time where the "now" date literal is returning standard
> time even though the OS (Windows NT) is configured correctly and and the
> operating system reports the correct time.

> Pat Coffer wrote:

> > At a few of our customers' sites we are having a problem since the start
of
> > daylight savings time where the "now" date literal is returning standard
> > time even though the OS (Windows NT) is configured correctly and and the
> > operating system reports the correct time.

> FWIW, I just tried:

> select cast('now' as date) from rdb$database

> ...against a 5.6 server running on NT 4 and got the correct time.

> -Craig

> --
> Craig Stuntz (TeamB)       Senior Developer, Vertex Systems Corp.
> Delphi/InterBase weblog:   http://delphi.weblogs.com
> Use Borland servers; posts via others are not seen by TeamB.
> For more info, see http://www.borland.com/newsgroups/genl_faqs.html

> E.g.:
>     Windows NT is set up for US Eastern, Automatically adjust for daylight
> savings time, current time = 13:00.
>     13:00 appears in the icon tray.
>     At a command prompt, the "time" returns 13:00
>     The following stored procedure returns 12:00 (in ISQL you have to turn
> on BasicSettings|Show Time Datatype):

>         create procedure get_server_time returns (servertime date)
>         as begin
>             servertime = "now";
>         end

> OS is Windows NT4 (waiting to find out what service pack, but probably 6)
> Interbase 5.6

> Is anyone else having this problem?  Our customers have been using
Interbase
> for three years and this problem has never occurred before.  It is also
not
> occurring at all sites.

> Thanks,
> Pat

> select cast("now" as date) from any_table

> returns the time one hour behind.  We did not have this problem last year.
> I'm wondering if it is some kind of belated Y2K bug?

> "Pat Coffer" <pcoff...@flash.net> wrote in message

> > E.g.:
> >     Windows NT is set up for US Eastern, Automatically adjust for
daylight
> > savings time, current time = 13:00.
> >     13:00 appears in the icon tray.
> >     At a command prompt, the "time" returns 13:00
> >     The following stored procedure returns 12:00 (in ISQL you have to
turn
> > on BasicSettings|Show Time Datatype):

> >         create procedure get_server_time returns (servertime date)
> >         as begin
> >             servertime = "now";
> >         end

> > OS is Windows NT4 (waiting to find out what service pack, but probably
6)
> > Interbase 5.6

> > Is anyone else having this problem?  Our customers have been using
> Interbase
> > for three years and this problem has never occurred before.  It is also
> not
> > occurring at all sites.

> > Thanks,
> > Pat

>The C runtime library version 5.x has a bug in it in which it
incorrectly
>calculates the beginning date for daylight savings time when daylight
>savings time falls on April 1.  Version 6.x of the C runtime does not
have
>this bug.

>Interbase 5.6 installs version 5.00.7303 of the C runtime, overwriting
any
>version that previously exists, even though the existing runtime may be
>newer.  This problem will not occur on W2K because of the Windows File
>Protection feature in W2K that replaces system files that are
overwritten by
>rude installers.

>To solve the problem, overwrite your MSVCRT.DLL with version 6.x.  I've
>tried 6.0.8397 and 6.0.8337 and they both solved the problem.  There
may be
>other versions that solve the problem as well.