Ok, I got an answer from a fellow CT member, but it's news to me, i honestly believed that it was possible to support all 3 values (note: i always use booleans as true/false, and don't allow null's, so have not encountered this before).

Answer:

"Yes, when using a nullable bit field on the db you actually only have two possible values: true or NULL. This is because we use NullBolean = false, so whenever a false is passed it will be converted to null. Given you use the GetNull(...) method.

Since Boolean only accepts two possible values True and False I can't see a workaround for this, without changing the related type.
When using booleans I always try to rely on ONLY two possible values 1/NULL, 1/0."

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Found a relatively easy fix to my issue thanks to Ged over at vbcity.com which is to replace my boolean properties of my object with an enumerable.

In my infoobject.vb after "END CLASS" but before the last line I put in:

Public Enum MyOwnType
  No
  Yes
  Null
End Enum

This enum assigns the value of 0 for "no", 1 for "yes", and 2 for "null"

Then I replace the boolean type in my object with type MyOwnType (which can hold only the three values I specified).

I use Cathal's suggestion for the Constructor and set _myproperty = myowntype.null so that it's set to NULL if it isn't specified outright in an instance of an object.

I do not use the Getnull() in the SqlDataProvider when passing this field.

Then in my AddObject Stored Procedure I change the @myproperty from bit to int.  I do a check for the passed variable and it it is "2" then I set it to null before it's inserted into the database.  That way I don't have to change my datatypes in the database from boolean.

Basically, since the Boolean type doesn't do what it should (in my opinion), I just create my own type and use that.

---

I'm too poor for anything other than the community version