🚀 go-pugleaf

In article <36e74b65.17766972@forums.inprise.com>, Steve Koterski 
politely paraphrased ...
> 
> >But only if you use the slash as separator, if you use the dot, it works. 
> >It seems to think it's US dates only when it sees the "/"
> 
> Holy sheep doo-doo, Batman!
---
We are not going to start a sheep-thread, aren't we? <G>
> You are correct and I have empirically
> confirmed this behavior (which satisfies my penchant for cynical doubt --
> no offense intended).
---
I have a 'penchant' for the same vice,;-) so I forgive you.

> With a Windows setting for Short Date Style of dd.MM.yyyy and a Date
> Separator setting of a period (.), local SQL will indeed accept DATE and
> TIMESTAMP literals where the date is in this format.
> 
>   SELECT OrderNo, SaleDate, EXTRACT(MONTH FROM SaleDate) AS MM
>   FROM "Orders.db"
>   WHERE (SaleDate BETWEEN "01.01.1998" AND "31.05.1998")
> 
> However, with a Windows setting for Short Date Style of dd-MM-yyyy and a
> Date Separator setting of a period (-), the same dates no longer work.
> 
>   SELECT OrderNo, SaleDate, EXTRACT(MONTH FROM SaleDate) AS MM
>   FROM "Orders.db"
>   WHERE (SaleDate BETWEEN "01-01-1988" AND "31-05-1988")
> 
> This would appear to be a short-coming in how the SQL parser used by the
> 32-bit BDE works with these literal values in conjunction with Windows
> system settings.
--
It doesn't like mixes.<G>

> I will correct the related information in the local SQL online help file
> forthwith!
Thanks.
-- 
Romain Strieff [TeamB]
Please read this newsgroup guide below before 
posting on the private Inprise newsgroups.
http://www.inprise.com/newsgroups/guide.html
--