🚀 go-pugleaf

Are you using a MS Access database or not?  If you are then the enclosing 
characters (#) will be necessary, if your using a SQL setup then there not. 
Also, i've had major headaches with data / time in MS Access - this may be 
the same issue that you are experiencing.

What I found is that if you do not explicitly define, within MS Access the 
format for the date, it can change from what system to another depending on 
the users settings - for some unknown reason! This also has an impact on the 
format of that date / time that you provide in your SQL statement.  You 
would assume that some conversion would occur at some point but it doesn't 
seem to in Access.

For example, if you look at your database and the date / time is stored as 
YY-MM-DD HH:NN:SS and you issue an SQL command with the date / time as you 
have (#2004/01/01 14:55:09#) - it may well fail, event though it works fine 
in the MS Access IDE / SQL Builder (some conversion must go on here).  Even 
if you were to ensure that the date / time in your SQL statement matched, 
when you deployed your application, the target user may have a different 
date format which would then cause the same problem again.

The only consistent way that I found to over come this problem is to specify 
an Format / Mask for each DateTime field within MS Access.  Then within your 
application, use the FormatDateTime function to ensure that you always 
'deliver', in you SQL, the date in that exact format.

HTH

Mike

"AW" <weichert@trios.de> wrote in message 
news:44eacbac@newsgroups.borland.com...
> Hello !
>
> I want to insert a DateTime criteria as a filter in a ADODataSet.
>
> This example works direct in MSAccess correct but not in a ADODataSet
> select IDData from tbldata where DateTime = #2004/01/01 14:55:09#
>
> How to format the DateTime ?
>
>
> Thanks
> Andreas
>