By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,694 Members | 2,121 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,694 IT Pros & Developers. It's quick & easy.

Elookup vs Dlookup, Error 3048

P: n/a
I have read with interest the many discussions of the 3048 Error:
Cannot open any more databases. I understand how the number of open
Table ID's causes the problem. My question has to do with the usage of
the Elookup routine as a substitute for Dlookup. I read that Dlookup
'does not clean up after itself'. Most of the discussion centered
around the use of Dlookup in queries or in the controlsource of form
and report controls.

My question is should I also replace my uses of Dlookup in code also,
or do code references not contribute to the problem?

Interestingly enough, I am seeing the error show up at a Dlookup in the
code of a form. I could interpret this to be just that the Dlookup is
the victim, if you will, of the fact that the number of allowed table
Ids was already met, or that each time a dlookup is executed in any
code, it adds one to the number of table IDs and they never get removed
from the Table ID count. I'd really appreciate spcific information on
this, if anyone has it.

My many thanks to the veteran,knowledgable contributors to these
groups. TIA,

Christine

Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I'm not certain how you are leveraging the dlookup, but if you can remove it
and add the targeted table/query to your source query, that is ALWAYS a
preferred solution.

Good luck,
Curt

<ct******@stny.rr.com> wrote in message
news:11*********************@g49g2000cwa.googlegro ups.com...
I have read with interest the many discussions of the 3048 Error:
Cannot open any more databases. I understand how the number of open
Table ID's causes the problem. My question has to do with the usage of
the Elookup routine as a substitute for Dlookup. I read that Dlookup
'does not clean up after itself'. Most of the discussion centered
around the use of Dlookup in queries or in the controlsource of form
and report controls.

My question is should I also replace my uses of Dlookup in code also,
or do code references not contribute to the problem?

Interestingly enough, I am seeing the error show up at a Dlookup in the
code of a form. I could interpret this to be just that the Dlookup is
the victim, if you will, of the fact that the number of allowed table
Ids was already met, or that each time a dlookup is executed in any
code, it adds one to the number of table IDs and they never get removed
from the Table ID count. I'd really appreciate spcific information on
this, if anyone has it.

My many thanks to the veteran,knowledgable contributors to these
groups. TIA,

Christine

Nov 13 '05 #2

P: n/a
Are you cleaning up after yourself in your code? For example, when you
declare an object and set it, are you setting it to Nothing in your
cleanup routine? If not, find all the SETs in your code and make sure
you set all of those back to Nothing to release the memory/handles.

Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.