IF statement from Access query

I am switching our Access queries to SQL views. How do I make this Access
97 "IF" statement a SQL 7 "criteria"?

FollowUp: IIf(IsNull([acct id]),"","Awaiting Follow Up")

Any help is very appreciated.

Eric <ericb@tfillc.com> wrote in message news:39c24ce1$1@news.devx.com...
>
> I am switching our Access queries to SQL views. How do I make this Access
> 97 "IF" statement a SQL 7 "criteria"?
>
> FollowUp: IIf(IsNull([acct id]),"","Awaiting Follow Up")
>
> Any help is very appreciated.

CASE [acct id] WHEN NULL THEN "" ELSE "Awaiting Follow Up" END

--
Colin McGuigan

"Colin McGuigan" <colin@chicor.com> wrote:
>Eric <ericb@tfillc.com> wrote in message news:39c24ce1$1@news.devx.com...
>>
>> I am switching our Access queries to SQL views. How do I make this Access
>> 97 "IF" statement a SQL 7 "criteria"?
>>
>> FollowUp: IIf(IsNull([acct id]),"","Awaiting Follow Up")
>>
>> Any help is very appreciated.
>
>CASE [acct id] WHEN NULL THEN "" ELSE "Awaiting Follow Up" END
>
>--
>Colin McGuigan
>
>
>
Thanks, Colin, but I get an error message: "CASE statement not supported".

Any other ideas?

Eric <ericb@tfillc.com> wrote in message news:39c25b29$1@news.devx.com...
> Thanks, Colin, but I get an error message: "CASE statement not supported".
>
> Any other ideas?

You're using SQL Server's poor excuse for a View Designer, aren't you? The
error is a 'Query Definitions Differ' error, or a 'SQL Syntax Errors
Encountered' error?

If so, the 'not supported' bit is just telling you that the View Designer
can't parse the statement. It doesn't mean it's invalid. If it's 'Query
Definitions Differ', just click 'Yes'. If it's 'SQL Syntax Errors
Encountered', just ignore it. If you look at your list of views, it should
show up just fine.

--
Colin McGuigan