At 11:52 PM 4/05/2003 -0400, you wrote:

Sorry, I told you wrongly about the hyphenated format. It's the ~~ dotted
~~ format you use to guarantee correct interpretation of dd.mm.yyyy.

>If I try to insert a date like "31-07-1995", isql returns an error
>"conversion error from string..."

Yup.

>If I enter a date like "07-30-1995", FB accepts the record, and a select
>returns a "1995-07-30".

It *should* be a fluke but, if you don't get a conversion error, then it
must be OK.

>If I enter a date like "1995-07-30", FB accepts the input, and a select
>returns "1995-07-30".

YES. To my knowledge, IB/Fb accept hyphens in this (ISO) literal format
and in the dd-MMM-yyyy literal format.

>If I enter a date like "30.07.1995", FB accepts the input, and a select
>returns "1995-07-30".

Correct, that's what I was trying to say before, except my mind went. :-(

>If I use my Access 2000 front end to enter data to the FB database through
>the XTG ODBC driver, none of the above formats is considered within range.

If the driver isn't interpreting the following literal strings correctly,
then the driver has a problem:

dd.mm.yy or dd.mm.yyyy
mm/dd/yy or mm/dd/yyyy
yyyy-mm-dd or yyyymmdd (it should accept either of those)
dd-MMM-yyyy

Did you try yyyymmdd? If not, I suggest you do, since the driver was
written by Czechs and I *think* this is the standard date format in the
Czech Republic - by which I mean that, no matter what other formats have
been tested, one would suppose that they tested *that* one.

You do know that date literals must be enclosed in SINGLE quotes, right?

Sorry for the misleading comments in the previous reply...

heLen