Hi Tiberius



You can use domains for this!

Define your domain as timestamp and change the table:

CREATE DOMAIN DT_DATE AS TIMESTAMP;



update RDB$RELATION_FIELDS set

RDB$FIELD_SOURCE = 'DT_DATE'

where (RDB$FIELD_NAME = 'CI_ELIBERAT_DATA') and

(RDB$RELATION_NAME = 'ASIGURAT');



update RDB$RELATION_FIELDS set

RDB$FIELD_SOURCE = 'DT_DATE'

where (RDB$FIELD_NAME = 'DATA_NASTERE') and

(RDB$RELATION_NAME = 'ASIGURAT')





Best regards,

Paul



From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Tiberiu Horvath
Sent: 03 June 2008 17:51
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Firebird Unavailable Database



You are right, I started using Interbase 6.02 and moved to Firebird.

I don't know anything about any DATE field problem. It works fine at many of
my customers. Should I modify all DATE fields to TIMESTAMP ?

Tiberiu

----- Original Message ----
From: Alan McDonald <alan@... <mailto:alan%40meta.com.au> >
To: firebird-support@yahoogroups.com
<mailto:firebird-support%40yahoogroups.com>
Sent: Tuesday, June 3, 2008 1:00:01 PM
Subject: RE: [firebird-support] Firebird Unavailable Database

> OK, the information :

I won't bottom post here...
I see you started with interbase and moved right up to FB2
You use DATE
You used DATE in interbase dialect 1?
What did you do to the data in the DATE fields when you migrated to dialect
3? Anything?
Remember that dialect 1 date is not the same as dialect 3 date.

If you backup dialect 1 DATE and restore dialect 3 DATE you don't get any
error (or you used not to - I haven't done this lately). But I do remember
that you need to properly truncate the contents of the fields or pump them
properly into a dialect 3 TIMESTAMP (the equivalent)

Did you did this?

Alan





[Non-text portions of this message have been removed]