[AccessD] IIf in query discussion

Completely agree.  I would add to that, however, that if you are going to
Nest IIF statements, to instead use an If Then Else structure within a
function, because nested IIF's can be a REAL pain to backtrack through.

Drew

-----Original Message-----
From: Susan Harkins [mailto:harkins at iglou.com]
Sent: Monday, March 31, 2003 2:25 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] IIf in query discussion


Rookie mistake? I don't know if I'd call it that. Data's unique and the
situation matters as much as anything else. An Iif might slow things down,
BUT if you're not working with tons of data and it's the solution you think
of first and there's no perception of a performance hit, what's rookie about
it?

Susan H.


Recently I read an article by an Access expert who suggested that using
'iif' in a query is a rookie mistake.

I've made that mistake.

My question: Does using 'iif' in a query just slow done processing, or, does
it have more substantial consequences?

TIA,
Myke




----------------------------------------------------------------------------
----


> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com