When using the business object mapper and setting the business object properties using SQL Server as the data source the table fields are not mapped\added.  There are two fields in the table that are of type numeric 9,2.

If I use the Database Development Toolkit it will map the fields.  When using the business object there is a "Specified cast is not valid" message for the numeric fields.

I know I should use a currency field, and I will be changing this.  I just wanted to point this out incase it is an issues that needs to be looked into.

So, the SQL Server database has a field type of Decimal(9,2)?



Are you getting this error message at runtime, or when the Business Object Mapper is generating the partial class?



What I mean is, does the Business Object Mapper properly create the partial and then you get the error when you access the field, or do you get the error message when you choose "Rebuild Partial" within the Business Object Mapper?

Scott,

Thanks for the tip.  This has been fixed and was actually caused by .NET excluding the Numeric data type from the SqlDbType enumeration.  I suppose they don't want us using the numeric type anymore.  At any rate, this has been fixed in the update that is now available through the downloads. 

Hya.

No need to look at this now. Just to say I'm facing this "Decimal" data type problem, at run time.

Thanks for the heads up, Ivan... I'll take a look at it.

As am I

Keith Chisarik

I am getting errors trying to save values to a decimal(6,2) field.



I tried changing the type to money, BO Mapper still shows it as decimal.



What do we use for numeric fields?

Keith Chisarik

nevermind......I had one field set to scale of zero. my bad.

Keith Chisarik

That's good because I could not figure out what was going on here...I will get out of my test now

actually it was another developer here I was helping.... I would never make such an error

Keith Chisarik