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

IsQueryTable suddently don't work

P: n/a
Hi

I have used the isquerytable function mentioned elsewhere for a few of
my databases. And there has never been a problem - but suddently the
code stops at:

test = db.TableDefs(TName).Name

with the fault:runtime error 3265 - the element was not found in this
collection. - and it does that with all my databases using the function
- although they used to work perfectly.

Does anyone know what can be wrong?

TIA
Jens

Oct 24 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a

JensT wrote:
Hi

I have used the isquerytable function mentioned elsewhere for a few of
my databases. And there has never been a problem - but suddently the
code stops at:

test = db.TableDefs(TName).Name

with the fault:runtime error 3265 - the element was not found in this
collection. - and it does that with all my databases using the function
- although they used to work perfectly.

Does anyone know what can be wrong?

TIA
Jens
I suspect that your code relies on triggering a handled error to work.
Either from the VBA window menu or in code you've turned on the 'Break
on all errors' option. From the VBA window, click Tools, Options, then
click the General tab on the Options dialog. Under 'Error Trapping'
select 'Break on Unhandled Errors'.

Bruce

Oct 24 '06 #2

P: n/a

de***************@gmail.com skrev:
JensT wrote:
Hi

I have used the isquerytable function mentioned elsewhere for a few of
my databases. And there has never been a problem - but suddently the
code stops at:

test = db.TableDefs(TName).Name

with the fault:runtime error 3265 - the element was not found in this
collection. - and it does that with all my databases using the function
- although they used to work perfectly.

Does anyone know what can be wrong?

TIA
Jens

I suspect that your code relies on triggering a handled error to work.
Either from the VBA window menu or in code you've turned on the 'Break
on all errors' option. From the VBA window, click Tools, Options, then
click the General tab on the Options dialog. Under 'Error Trapping'
select 'Break on Unhandled Errors'.

Bruce
This was exactly the problem - thanks a lot Bruce

Oct 24 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.