daelmo wrote:
As a matter of fact it should be mapped as decimal (you can confirm that on msnd ado.net docs).
Thanks, I found the docs here:
http://msdn.microsoft.com/en-us/library/cc716729.aspx
What do you want it mapped as float?
I am using those fields for simple percentages that will have a precision of 5 with a 2 digit scale (so I can represent ###.##). In that case, perhaps a Decimal is overkill and I should instead use a Real in SQL Server?
To me it seemed that since I was working with such a small Decimal (with precision = 5), I thought that I would be able to select a different compatible .NET type such as a Single. I see now that if I keep with the Decimal type that I'll have to provide a typeconverter.
I'll have to do some testing in using a Real instead of a Decimal within SQL Server. Do you have any thoughts on the datatype given what I mentioned above I would be storing?
Thanks,