No, I changed it to a DateTime in the designer line but it changed back to a SmallDateTime when I rebuilt the partial.  For whatever reason it just won't let go of that original SmallDateTime type.  Let me know what you find out...hopefully I can get a fix for this so I can continue working on this piece of code.  Thanks for the help!

OK, I've been looking through the code that generates the partial classes for business objects, and the only SQL data type that uses SmallDateTime is SmallDateTime.  So, it could be that your business object is mapped in the BOMapper to a DDT profile rather than the actual SQL Server and the field is still SmallDateTime in the DDT.  Or vice versa, it's mapped to SQL Server and the actual field's data type wasn't changed.  If the actual source of the column is properly set to SmallDateTime, then there must be a problem with the GetSchema() method of the SQL Server connection returning the proper value.

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