Use of DSum, DCount, DLookup, etc in form after splitting

[QB]

I was reviewing Tony's Performance FAQ and am trying to address point 'Use of
DSum, DCount, DLookup, etc in form after splitting' That said the link he
provides is broken. Before I reinvent the wheel, I thought I ask if/where
others had found good replacement functions?

I know and use Allen Browne's Elookup (great function)

But am interested in DSum, DCount,...

Also, for personal knowledge, why is native functions such as these slower
than user defined functions??? I find this very weird and MS has never fix
this in its' multiple versions ...?

Thank you,

QB

 

[Jeanette Cunningham]

I haven't heard or found that DSum and DCount are any slower after splitting
or slower than user defined functions.
These functions are very useful and often used - however if you have a lot
of these functions in a form, then maybe you need to look at your database
structure or include those fields in the recordsource of the form.

DCount is fast when you are using an indexed field such as checking the
count of the primary key of a table where certain criteria are met and those
criteria are also indexed.
If using a non-indexed field it would be slower.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia