dlookup, dcount and Slect SQL

[Souris]

In my appilcation I need use Dlookup or Dcount to get information from
database. I would like to know from performance of view, are Dlookup, DCount
or use SQL statement are better choice for the applications?


Your information is great appreciated,

 

[Ed Metcalfe]

In my appilcation I need use Dlookup or Dcount to get information from
database. I would like to know from performance of view, are Dlookup,
DCount
or use SQL statement are better choice for the applications?


Your information is great appreciated,

DLookup and DCount (and all the other domain aggregate functions) are okay
on tables with very few records), but as a general rule they are *much*
slower than a SQL SELECT.

Ed Metcalfe.

 

[Souris]

DLookup and DCount (and all the other domain aggregate functions) are okay
on tables with very few records), but as a general rule they are *much*
slower than a SQL SELECT.

Ed Metcalfe.

 

[Souris]

Thanks millions

DLookup and DCount (and all the other domain aggregate functions) are okay
on tables with very few records), but as a general rule they are *much*
slower than a SQL SELECT.

Ed Metcalfe.

 

[Souris]

Thaks for the information,

So I need assign to a recordset from SQL statement and use recordset.fields
to retrieve infromation from SQL statement.

Am I right?
Please let me know if I am wrong,

Thanks again,

 

[Rick Brandt]

DLookup and DCount (and all the other domain aggregate functions) are
okay on tables with very few records), but as a general rule they are
*much* slower than a SQL SELECT.

This is an often repeated myth.

Domain aggregates are ill-advised in queries and in looping operations.
That is because there is a certain amount of overhead that is incurred per
use of a domain aggregate function and in a query or looping operation that
overhead piles up and becomes noticeable.

As long as you are not in a query or looping operation then they are just as
fast as using a Recordset.