Hi,
I have a webpage accessing a sql database where it checks whether a user is currently logged in(its a sql boolean type).

when users are created its null(lord knows why those DBA's wont default it),anyway,the first time its NULL ,and when I do a select on it ,it threw an error(cause iwas trying to cast it to VB.NET boolean);

however,the next time I select it ,it works!!Its one of those What-The-Hell type things?

Maybe someone knows more,if so,please tell me about it.


regards,
KB

Hey,

When you access it, do you use:

if (not objRow.IsNull("boolean")) then

end if

I would recommend that when accessing a nullable field. You can't add a default value of 0 or 1 to the table column?

Brian

I am going to do that from now on.just that it doesnt seem right that sql wouldn't do it the first time,but works the second time(both time only SELECT)

Was it the same exact query? That shouldn't be right? Did anything change, even minute?

It was the same query;nothing changed;except maybe a minute's delay in navigatin back to login page and re-try.
now i have that null check in place.
Is this thing bound to happen with a dataset also? if so how to check whether tables exist inside the ds?

Hey,

Well, no, whether rows are returned or aren't, the dataset will have one table. The table just will have rows or won't have rows.

Brian