I have a BO which has a date field.  Previously, it was a SmallDateTime field in the database.  I started getting an error when trying to put a value of 01/01/1800 in it for a null, so I changed the type to be a DateTime to make it accept the value.  I rebuilt the partial BO, and recompiled.  I am still getting an exception saying that there is a SmallDateTime overflow exception.  I can put the 01/01/1800 date in if I do it directly through Query Analyzer, but when I do it through the BO it still thinks the field is a SmallDateTime for some reason.  It's like it isn't recognizing the type change, but all I see on the type in the BO code is System.DateTime.  Is there something I'm missing here or something I'm not doing?

The exception is coming from the SaveByForm routine in BusinessLayer.vb and it reads as follows:  SqlDbType.SmallDateTime overflow.  Value '01/01/1800 00:00:00' is out of range.  Must be between 1/1/1900 12:00:00 AM and 6/6/2079 11:59:59 PM.

OK, I think I've found the issue.  In the designer code of the BO, inside the New()...there is a block of FieldNativeDbTypes.Add methods for each field.  The field in question still has this line of code:

_FieldNativeDbTypes.Add("InsurerExpire", System.Data.SqlDbType.SmallDateTime)

I think this may be a bug because it should be changing that back to DateTime if I rebuild the partial shouldn't it?

 

Hmmm...yes you are correct.  I will have to look into this.  If you remove that field descriptor class and rebuild the partial, does it show back up correctly?  Or, if you just change it to represent a DateTime and rebuild the partial does it leave it alone?  In either case, I am glad you found your problem.  I will look into this from a BO Mapper perspective.