Michael R Mattys
michael.mattys at adelphia.net
Mon Mar 31 14:08:09 CST 2003
I may learn something new here. What are the alternatives? Functions with paramarray variables? More precise SQL statements? Else? Michael R. Mattys www.mattysconsulting.com ----- Original Message ----- From: "John Bartow" <john at winhaven.net> To: <accessd at databaseadvisors.com> Sent: Monday, March 31, 2003 3:14 PM Subject: RE: [AccessD] IIf in query discussion > MessageYou probably need to give us more details but I tend to agree in > philosophy with the idea that IIF should not be used unless necessary. But > in practice it is sometimes necessary. I have it used it mostly when > querying a pre-existing database which is poorly normalized (hmmm, that > might be an oxy-moron). I use it as a guideline not a rule though, the only > "rule" I tend to have is to never rule out anything. > > I think the biggest drawback beyond speed is that its Access specific and > they can be difficult to read. I think "spreadsheet people" love it though. > > JB > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] > Sent: Monday, March 31, 2003 1:39 PM > To: accessd at databaseadvisors.com > Subject: [AccessD] IIf in query discussion > > > 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 >