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, for some reason you made me think of what I was doing wrong here.  We have LOTS of databases that we use, and I was simply looking at the one I was running with and not the one I was mapping to.  I kept changing it in the one I was running with, so of course when I stepped through code it was changed.  But, the BO Mapper was still getting the SmallDateTime because I hadn't changed it in the mapped db.  Now I feel dumb...haha.  Sorry for the false alarm, but thanks for helping me through it.

No problem   We do that all the time.  In fact, Steve and I were working on one yesterday and kept getting an error sayind that field such-and-such wasn't part of the table... ???  Well, as it turns out, we had just that morning moved our connection string over to a different database that contained some test data.  Spent well over an hour stepping through the code thinking there was a bug