[AccessD] Dlookup - where parameter being a form control vs a function

[Jim Dettman]

Paul,

 Just to add one other thing; keep in mind too that the Domain functions
were intended to be used in places where SQL statements were not allowed,
such as a control expression.

 If you are working in code, then you can use SQL and open a recordset
yourself, which is usually faster.  If you are working in a query, then you
are working with SQL directly anyway.   In fact here it's a really bad idea
to use a domain function as it's totally un-optimizable by the query parser
(there are some rare cases where you might want to, such as trying to make a
form editable, but it's not a great idea).

Jim. 

-----Original Message-----
From: AccessD On Behalf Of Gustav Brock via AccessD
Sent: Friday, May 21, 2021 2:36 AM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Cc: Gustav Brock <gustav at cactus.dk>
Subject: Re: [AccessD] Dlookup - where parameter being a form control vs a
function

Hi Paul

Don't waste your time on this. The speed increase, if any, is not worth the
efforts.

/gustav 
-- 
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com