alternative of dlookup and aggregate in spllited database

[accessonly11]

dear members,
some of mvps like Richard Rost recommand to avoid aggregate queries and dlookup functions in splitted database.
then what are alternative of these important features. please guide.

 

[arnelgp]

use allen browne's ELookup:
Microsoft Access tips: Extended DLookup() (allenbrowne.com)

or TLookup:
Solved - Replace Dlookup with as Sql Query | Access World Forums (access-programmers.co.uk)

 

[June7]

I have a split db that uses a ton of DLookup() expressions and never caused any issues.

As for aggregate query, maybe a report and do aggregate calcs on report.

 

[ebs17]

avoid aggregate queries and dlookup functions in splitted database

Such blanket statements are regularly stupid. There are reasons why such solution methods exist, and there are configurations where such solution methods can show weaknesses. It is up to the developer to distinguish between them.

In a splitted database we have the possible situation that there is a slow network between frontend and backend. Jet (Access-SQL) processes data locally in the frontend, so it has to pull it from the backend, in unfavorable configurations multiple times. So when the network becomes a bottleneck, existing problems with your own programming and query design are exacerbated and then become much more noticeable, often through degraded performance.

To put it the other way around: Grouped queries and dlookup functions can also be a bad thing in an unsplitted database. It depends on the specific use.