Re: Function Vs Expressions

Jose Perdigao wrote:
I don't understand why domain aggregate functions is slower than
expressions, they should be faster because is aggregated in access.

There is overhead associated with the use of a domain aggregate function. When
used singularly in code or a form/report expression this overhead is not an
issue. When used in a loop or a query that overhead is incurred for each and
every row or loop iteration and then it becomes a significant performance
problem.


--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com


.

Relevant Pages

  • Re: Function Vs Expressions
    ... form to entry data and from the calcultaion result store it in a field. ... Normally, i don't store the calculations results to save memory, but I ... There is overhead associated with the use of a domain aggregate function. ...
    (microsoft.public.access.formscoding)
  • Difference between = and IN
    ... I am aware that '=' compares two expressions whereas 'IN' looks to see if an ... is quicker to type than one with an 'IN'. ... Is there an overhead associated with ...
    (microsoft.public.sqlserver.mseq)