SQL Function returning boolean value

That's not my problem, Aneesh.
I have a function that returns a BIT, I want to make it return a boolean, for use in:

SELECT CASE WHEN dbo.myFunc()   <---- fails because it is not a boolean expression
THEN .....
ELSE ......
END

You need to compare the values from the Function

SELECT CASE WHEN dbo.udfFunction(10,1)=1 THEN 'true'  ELSE 'False' END

I know, but that's exactly what I want to avoid

There is no provision in SQL server to do this even in IF statement also you need to put the condition

The syntax of CASE..WHEN

CASE
    WHEN Boolean_expression THEN result_expression

So it must be a boolean expression and the function just returns a 'Bit'

I know all you are telling me, I am not a principiant.
My question is "HOW TO RETURN A BOOLEAN VALUE INSTEAD A BIT"

From Access Help:  Boolean Data Type
     
Boolean variables are stored as 16-bit (2-byte) numbers, but they can only be True or False. Boolean variables display as either True or False (when Print is used) or #TRUE# or #FALSE# (when Write # is used). Use the keywords True and False to assign one of the two states to Boolean variables.

When other numeric types are converted to Boolean values, 0 becomes False and all other values become True. When Boolean values are converted to other data types, False becomes 0 and True becomes -1.

Are you linked to SQL Server from Access?  In which case you can convert the SQL Bit value to Boolean using the Access function CBool() in a query.  Using a Select query, you are not changing the SQL Server data, but you can obtain Boolean type results using the conversion.  Is this of any help or have I completely missed the mark?

To GrayL,
I am working with C# and MSSQL Express 2005, but I am trying to solve this at Server side.

To all,
Have you tried to trick the server by using a variant data type?

>To all,
>Have you tried to trick the server by using a variant data type?

yes, tried it, with the same result: it does not work.

Then I guess I have to ask why is this in the Access TA?

Oops, how did that happen?  Sorry guys, disregard my last remark.  I got carried over to another TA and didn't notice.

>>I know all you are telling me, I am not a principiant.
My question is "HOW TO RETURN A BOOLEAN VALUE INSTEAD A BIT"<<

A couple of comments:  
1. These two sentences contradict each other.
2. Do not use ALL CAPS, not even for emphasizing. It is just plain rude.  We are all here to help you and you may actually learn something.

Suerte.

To acperkins,
There is not contradiction. There is no other way to emphasize here at E-E, unless you know how to underline or colorize, I am curious.

To aneeshattingal and angelIII,
Thanks for exploring all possibilities

To GRayL,
You are right, this is not Access TA

>>There is not contradiction.<<
You misunderstood what I meant.  Perhaps it got lost in the translation.

>My question is "HOW TO RETURN A BOOLEAN VALUE INSTEAD A BIT"<<

I have to agree that it is NOT a contradition.

Boolean = TRUE or FALSE
Bit = 0 or 1

now, technically, boolean false is most often evaluated as 0, and true everything else (mostly 1 or -1 though)
hence, the 2 datatypes are not equal, but easily convertible.

>>I have to agree that it is NOT a contradition.<<
Let me restate what I said:
"These two sentences contradict each other."

In other words, How can you not be a "principiant" (from the Spanish word "principiante" and in English "beginner") in SQL Server and not know that the closest you have to a boolean in T-SQL is a bit data type?  That is the contradiction in terms.

Not from spanish "principiante" but form latin "principium". Maybe you have to review your raw-english-to-cult-english dictionary sometimes.

Webster Dictionary:
Prin·cip·i·ant
[L. principians, p. pr. of principiare to begin, fr. principium. See Principle.]
Relating to principles or beginnings.