I am using same language as DLookUp but in a control source of a text
field
(not VBA as in Allen Browne's example): Report opens with "ENTER
PARAMETER
VALUE: ELookUp"
Control source in TEXT field in report reads:
=ELookUp("[TABLE NAME]","AAADIAGRAM","[TABLE NUMBER]=TABLE1")
another TEXT field/control source identifies TABLE1
I should explain why I'm using ElookUp:
We successfully have used DLookUp for years in reports using above
programming/syntax (in both access 2002 & 2003).
Have recently had trouble with "The Search key was not found in any
record".
In these reports, not accepting changes, deletions, name changes etc.
First suggestion was checking reference but we had already checked off:
ActiveX Data Lookup & DAO 3.6. Sometimes just opening references and
clicking OK and saving does help problem, but we can't rely on that.
So.Second suggestion: DLookUp was causing issues should use ELookUp
instead?
Would appreciate any thoughts you have!!! Thanks in advance!
--
tgl
Douglas J. Steele said:
You talking the function Allen Browne has at
http://www.allenbrowne.com/ser-42.html?
I don't see any reason why it shouldn't work. What happens when you try
to
use it?
--
Doug Steele, Microsoft Access MVP
(no e-mails, please!)
we use reports in Access 2003 that use DLOOKUP in text box/control
source.
ELOOKUP does not appear to work in this situation, is that correct???
thanks in advance!