🚀 go-pugleaf

On Fri, 05 Mar 1999 22:17:33 GMT, skoterski@NOSPAMinprise.com (Steve
Koterski) wrote:

>On Fri, 05 Mar 1999 21:30:21 GMT, skoterski@NOSPAMinprise.com (Steve
>Koterski) wrote:
>
>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.

So VdB did after all not do any hanky-panky. Well I am learning all
the time.

>
>Okay. So here is the rewrite of the date topic for the online help.
>

Thank you. It is good to have official confirmation (and so quickly!)
that use of european dates in the way you describe is not due to a
bug, but is a feature of the BDE which works as designed.
 
>Which one of the two you use is predicated on the Windows
>configuration settings for Date Separator and Short Date Style.

For the unaware user this sentence seems to imply that he must change
the settings in the Windows configuration if he is going to work with
a date format different from the one he is using at the moment. In VdB
date settings are handled by at set of specific commands. Would it be
acceptable to say:

"Which one of the two you use is predicated on the configuration
settings in Windows and/or the BDE-using front-end application."

> A combination of Short Date Style of month before day and a Date
> Separator of anything but a period is not supported in local SQL.

This sentence is difficult to understand as it contains two negations.
Are you saying that only a combination of month before day and a
period as date separator is supported? i.e. MM.DD.YY

>Example of a date literal in a US format:

The examples are fine.

Ivar B. Jessen