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

Error 2501 Top Tip

P: n/a
If you ever suddenly find that trapping Error 2501 when a report has no data
no longer works, don't do what I did and spend 3 hours looking for a
non-existent bug, simply check that the "Break in Class Module" option is
selected.

We recently had a change in IT provider and I'm guessing that some of their
hocus-pocus tampered with my Access settings ... GRRR!

Keith.
www.keithwilby.com

May 30 '07 #1
Share this Question
Share on Google+
6 Replies

P: n/a
On Wed, 30 May 2007 10:45:59 +0100, "Keith Wilby" <he**@there.com>
wrote:

That setting is machine specific. Did your IT firm make this
adjustment on your machine? Seems unlikely, but a handy scapegoat it
is.

-Tom.

>If you ever suddenly find that trapping Error 2501 when a report has no data
no longer works, don't do what I did and spend 3 hours looking for a
non-existent bug, simply check that the "Break in Class Module" option is
selected.

We recently had a change in IT provider and I'm guessing that some of their
hocus-pocus tampered with my Access settings ... GRRR!

Keith.
www.keithwilby.com
May 30 '07 #2

P: n/a
"Tom van Stiphout" <no*************@cox.netwrote in message
news:80********************************@4ax.com...
On Wed, 30 May 2007 10:45:59 +0100, "Keith Wilby" <he**@there.com>
wrote:

That setting is machine specific. Did your IT firm make this
adjustment on your machine? Seems unlikely, but a handy scapegoat it
is.
I've no idea Tom, all I know is that the error trap suddenly stopped working
and it roughly coincided with the takeover. It isn't a setting I'd change
and the new provider has brought all sorts of policy changes. I'm not
suggesting they'd do this on purpose but it might have been a side-effect
another change.

I have a question - if the setting is machine specific then will the error
handling fail on other machines if the "default" setting is "Break on all
errors" even though I've set the option otherwise? If it is machine
specific then it's not much use in this respect.

Regards,
Keith.

May 30 '07 #3

P: n/a
"Tom van Stiphout" <no*************@cox.netwrote in message
news:80********************************@4ax.com...
On Wed, 30 May 2007 10:45:59 +0100, "Keith Wilby" <he**@there.com>
wrote:

That setting is machine specific.
Tom, the help would tend to suggest otherwise:

"Specifies the settings, error handling, and compile settings for your
current Visual Basic project."

Regards,
Keith.

May 30 '07 #4

P: n/a
On Wed, 30 May 2007 16:36:07 +0100, "Keith Wilby" <he**@there.com>
wrote:

I wasn't sure myself, you I set it in project 1, opened project 2 and
it was set the same way, set it to another value and reopened project
1 and it was set to this other value. So I concluded it was machine
specific, not db specific.

-Tom.

>"Tom van Stiphout" <no*************@cox.netwrote in message
news:80********************************@4ax.com.. .
>On Wed, 30 May 2007 10:45:59 +0100, "Keith Wilby" <he**@there.com>
wrote:

That setting is machine specific.

Tom, the help would tend to suggest otherwise:

"Specifies the settings, error handling, and compile settings for your
current Visual Basic project."

Regards,
Keith.
May 31 '07 #5

P: n/a
On Wed, 30 May 2007 16:04:19 +0100, "Keith Wilby" <he**@there.com>
wrote:

Another change?
That would have to be a registry change (I'm thinking that's where
Access would save this option). Not impossible, but not very likely
either.

Are you sure you didn't set this option programmatically (SetOption)?

-Tom.
>"Tom van Stiphout" <no*************@cox.netwrote in message
news:80********************************@4ax.com.. .
>On Wed, 30 May 2007 10:45:59 +0100, "Keith Wilby" <he**@there.com>
wrote:

That setting is machine specific. Did your IT firm make this
adjustment on your machine? Seems unlikely, but a handy scapegoat it
is.

I've no idea Tom, all I know is that the error trap suddenly stopped working
and it roughly coincided with the takeover. It isn't a setting I'd change
and the new provider has brought all sorts of policy changes. I'm not
suggesting they'd do this on purpose but it might have been a side-effect
another change.

I have a question - if the setting is machine specific then will the error
handling fail on other machines if the "default" setting is "Break on all
errors" even though I've set the option otherwise? If it is machine
specific then it's not much use in this respect.

Regards,
Keith.
May 31 '07 #6

P: n/a
"Tom van Stiphout" <no*************@cox.netwrote in message
news:i8********************************@4ax.com...
On Wed, 30 May 2007 16:04:19 +0100, "Keith Wilby" <he**@there.com>
wrote:

Another change?
That would have to be a registry change (I'm thinking that's where
Access would save this option). Not impossible, but not very likely
either.

Are you sure you didn't set this option programmatically (SetOption)?
No that I know of. It could very well be operator incompetence but I think
I'd have remembered making that change. Anyway, all is well now :-)

Keith.

May 31 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.