Hi Salvatore,
I'm also a "Windows only" user, but I don't think Windows should be
considered the gold standard and I don't think Firebird should adhere
to its behaviour.

Generally, dates in Firebird are stored as the number of days since a
certain date a couple of centuries ago. For input, it is true that
Firebird accepts certain normal string formats, but in general I'd say
you shouldn't rely on them. Using IBO through Delphi myself, I
normally use <fieldname>.AsDate and never <fieldname>.AsString. Then,
Windows or IBO do translate the date from the local setting on my
Windows machine to the internal Firebird format (I didn't check, but I
don't think it would have worked for me the last few years if it
didn't do this). It certainly does not bother me that it wouldn't work
if I used <fieldname>.AsString!

How nice that we do not have to quarrell whether the format should be
mm.dd.yyyy. dd.mm.yyyy, yyyy.mm.dd or even yyyy.dd.mm.

Set

--- In firebird-support@yahoogroups.com, "Salvatore Besso" wrote:
> hello all,
>
> I was wondering if it could be considered a bug the fact that
> Firebird accepts only "/" and "." as date and time separators. I
> verified this only now when an error was submitted to me by a user
> that was trying to insert a row with a date in the format
> "mm.dd.yyyy". This happened because that user has set "." instead
> of "/" as date separator in his Windows installation.
>
> Shouldn't FB handle different date and time separators like Windows
> does?