[dba-SQLServer] Date problem

Susan Harkins harkinsss at bellsouth.net
Fri Mar 10 16:17:04 CST 2006


Yes, I'm using T-SQL. The pro is simply a variable that represents the ADOX
Procedures collection. I declared dte as a Date data type. I'm with you
Billy -- I have never seen this kind of error when comparing dates before. 

I haven't looked at it anymore this afternoon. I'm going to test the
pro.ModifiedDate property setting and see what it's returning -- possibly
.Modified Date and Date aren't compatible? I don't know why they wouldn't
be, but it's the best I can come up with at this point. ModifiedDate may
possible be a DateTime, but you would think it would still reconcile the
difference. 

Susan H. 

P.S. Coffee is "do I want to date you" viewing time. :) 

is this in TSQL?  why is there a "pro." prefix in the expression? afaik it
should be technically possible to use < operator for date expressions.  
maybe it thinks either "pro.ModifiedDate" or "dte" is not a date.

Billy
ps. some people think having coffee is also not considered a date; only
movie and dinner





More information about the dba-SQLServer mailing list