Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
–1.#QNAN
- Thread starter Saama5
- Start date
if you are inserting the data through a stored proc and you are passing "–1.#QNAN" parameter as a varchar type, then you can check it out using: if isnumeric(@paramname) ...
if you are inserting it directly from a client program, then you should do the validation there before even sending it to sql server.
alfredp77
if you are inserting it directly from a client program, then you should do the validation there before even sending it to sql server.
alfredp77
- Thread starter
- #4
Thanks alfredp77.
I am not passing -1.#QNAN intentionally. It might be like ado when reading empty field from float data type or we loose network it is storing -1.#QNAN. We have done lot of checks on client program. Now I have given 0 as default value when we insert empty record. If any other clue please let me know. If we are passing 0 everytime then still it happens, I did not get it how it happens.
I am not passing -1.#QNAN intentionally. It might be like ado when reading empty field from float data type or we loose network it is storing -1.#QNAN. We have done lot of checks on client program. Now I have given 0 as default value when we insert empty record. If any other clue please let me know. If we are passing 0 everytime then still it happens, I did not get it how it happens.
- Status
Similar threads
