I appologize if I repeat some of the previous posts but I think they might be worth repeating... and I believe John Marks referenced the same URL that I do...

I see why people come to the conclusion that you must use FLOAT as an input to functions... what people should say on funtions is that you must not use...

Excellent reference, GP... though I'm not sure what you meant by "you have to use Float if your application need math functions".  If you meant that you are inherently using...

Nope... massive deoderant failure on my part 

Sure, Mick... Sorry for the previous all too brief post...

First, let me tell you that the others are absolutely correct... SMALLDATETIME is rounded to the nearest minute and you should...

Sorry, Tim... poor choice of words on my part.

You are correct... cannot attach files... nicely formatted code.  Welcome aboard!

It's things like this that make me appreciate a good old fashioned IDENTITY column...

PW beat me to it... don't use float for anything, if you can help it.  It's one of those "approximation" data types that are based on binary math. 

Now, what...

I guess I don't understand why no-one liked Ryan's first solution with the -275 thingy (although I'm not sure it will withstand a Leap Year).  It was very simple and...

You could easily turn this into a stored procedure or perhaps a table function...

--===== Define the input parameters

DECLARE @PropertyIDtoFind INT

DECLARE @MileageLimit DECIMAL(7,2)

    SET @PropertyIDtoFind = 183297

    SET...

Must be a nasty copy'n'paste error... The code doesn't work as posted...

GO must be the only thing on a line...

Every /* must be match with an */...

...

However, I agree...

Ken,

Your solution was fine, as well... I was responding to Fintan who apparently didn't read either of your posts very well.

Look at the SELECT!  That's where the meat of Ryan's example is...

Ryan's post was an example to demonstrate the method for using the "mon yyyy" format as a datetime that you...

Understood... you're not really changing the column type... just making it so it won't take bad data.  Most vendor apps can withstand this type of change even if they've made...