Try this:
fullDT = createDateTime(datePart('yyyy',userDate), 
datePart('m',userDate), datePart('d',userDate), datePart('h',userDate), 
datePart('n',userDate), datePart('s',userDate))
then your comparison becomes datefield > #fullDt#
Alternatively there is the createODBCDateTime function.  I know this 
means you are doing the same thing a different way but it could be one 
of those bugs.


Burns, John D wrote:

>I'm having some strange problems with a query I'm writing.  I've got
>data that can be inserted into a table quite a few times within a
>minute.  I'm trying to refresh a user's view automatically by passing in
>the last date/time that the person got data from the server.  I'm doing
>a simple query and my where statement says something along the lines of
>dateField > '#userDate#' and the query seems to be only comparing down
>to the minute, but not as precise as second or millisecond.  I was
>looking through the MSSQL docs and couldn't find anything on changing
>the precision of the dates that it would use or anything like that.  Can
>anyone offer advice?
> 
>John Burns
>Certified Advanced ColdFusion MX Developer
>AI-ES Aeronautics, Web Developer
> 
>
>
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Logware: a new and convenient web-based time tracking application. Start 
tracking and documenting hours spent on a project or with a client with Logware 
today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:190922
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to