>>Out of curiosity, I tried
>>
>>

select * from mylogins 
>>where logintime like '2013-08-06 17:51:18'

>>
>>and a few other combinations, with % in some places. No error, no result.
>>
>>Too bad - SQL server throws errors for all kinds of funny reasons, yet this goes by silently. And it could actually be useful for partial date search - when you know only the decade and month, or some other parts of the date. It's silly to use plain strings as date literals in the first place, and then even sillier to never fix the statement parser to not allow this. Yes, the argument to compare with is a string literal, but that doesn't mean that all operators that apply to strings make sense.
>
>
>Dragan,
>SQL server (and VFP too) wouldn't raise an error if there is no matching records to a given criteria. Thus SQL server, not giving any results, is more of a question here. The reason is that, really you wouldn't find any results for that given string and there is no error.
>
>If you read the documentation for LIKE it says:
>
>"If any one of the arguments is not of character string data type, the SQL Server Database Engine converts it to character string data type, if it is possible."
>
>A DateTime value is convertible to string, thus it is converted to check for a match (almost any types are convertible to string).
>
>Now try:
>
>

select * from mylogins 
>    where logintime like 'Aug 6 2013 5:51PM'
>
>select * from mylogins 
>    where logintime like 'Aug 6 2013%'
>

>
>Datetime default format is 100 (mon dd yyyy hh:miAM (or PM)).
>
>As per the blog pointed out by Greg, unfortunately anyone can write blogs with or without correct information in it.

Wow, didn't know this... even "where pk like '800%' " actually works and returns the expected result. Who'd a thunk...