> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Osborne
> Sent: Sunday, 3 October 1999 13:57
> To: Multiple recipients of list database
> Subject: Re: [DUG-DB]: [WARNING]: Converting TDateTimePicker.Date to
> ftDate TQuery Parameter
snip[
> Jeremy suggests converting dates to strings and building the SQL statement
> that way. My experience with that hasn't been good - it seems
> that in string
> format, SQL dates are expected to be in "mm/dd/yy" format in WHERE clauses
> regardless of your short date format. (Or is this just me and
> I've missed a
> config parameter somewhere?)
No, that is the ANSI SQL standard for date formats. Database Desktop for
example uses this format in SQL queries even though it will display the
results in the local format. Using parameterised dates (my current project
builds the SQL in code but puts in parameters and assigns the TParams)
simply lets you use a TDateTime.
Incidentally the TDateTimePicker declares both its Time and Date properties
to be in effect TDateTime which suggests maybe there is just one internal
TDateTime attribute that hold both and formats the Date and Time published
properties.
============================================
Patrick Dunford, Christchurch, NZ
http://patrick.dunford.com/
---------------------------------------------------------------------------
New Zealand Delphi Users group - Database List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
