Nikita Nikitich wrote:

> Now the wierd thing. Though machine's clock was correct, 'NOW'
> function in firebird was still one hour behind. And I noticed it
> only one day later. Stopping and restarting Firebird service solved
> the problem. But I still don't understand how this happened and keep
> wondering if the same thing will happen in November.

Most probably not.

> Can anyone explain what happened and should I worry about the
> future "fall backs" and "spring forwards"?

AFAIU, the Windows itself still feeds the "old" time to running
applications, only newly opened apps. get the "new" time, unless they
explicitly handle some kind of "change event". Thus the problem should
not happen again.

--
Milan Babuskov
http://www.guacosoft.com
http://www.flamerobin.org