Originally posted by: gunneyk
I don't think anyone here can answer that question definitively. You would have to ask the developer of the tool. My guess is that it was due to the difference in the underlying architecture and framework of the new .net based tools. SSMS in general was a rewrite and had to conform to a lot of the restrictions of Visual Studio and a lot of the codeing was done by non-database savy people. This is just one reason why the current version is less than optimal. And who ever wrote that portion most likely never used that functionality previously and never realized it was different. I looked again and don't see a configuration option to change the behavior. So it appears you will need to rethink your process.
I more than agree wiht this.
If you are able to, allways put down a value like a "zero" in stead of leaving stuff infinnity null.
And further, if you can code, then the statement in the tool should be "if null than nothing, nothing Or if null than 0 (zero)" will do the trick.
Just a matter of codeing and common sense.