> > > I am wondering about the date and time services in the FB engine,
> > > when the timezone is changed on the server hosting the FB engine.
> >
> > > Using
> > > a. FB 1.5.1.4481 on MS Server 2003 running as a sevice with
> Guardian
> > > also running.
> > > b. Win2K client with IBO 4.3Aa and delphi
> >
> > > An application asks the FB server for the FB CURRENT_TIMESTAMP
> and
> > > displays it.
> >
> > > On the server change the timezone to shift it several hours on
> the
> > > same day. During this leave the FB server running.
> >
> > > Back on the client ask for the FB Engine Current_Timestamp. It
> shows
> > > time for the previous timezone setting.
> >
> > Are both instances of fetching CURRENT_TIMESTAMP within the same
> > transaction? If your answer is yes, then there's your answer to
> your
> > question. CURRENT_TIMESTAMP is a transaction context variable,
> > basically it's gets assigned at the beginning of a transaction and
> > doesn't change until the transaction is committed or rollbacked.
> >
> > --
>
> Hello Daniel
> Successive calls to display the CURRENT_TIMESTAMP variable show the
> values's minutes changing. So the behaviour is not related to being
> inside a single transaction.
>
> At least it appears the FB engine is unaware of a manual change to
> its Win32 host's timezone.
>
> Kind regards
> Russell
>

Russell, were you comitting between this requests? Did you start a new
transaction?
Alan