Error 2501 No-brainer

[Keith Wilby]

In an old A97 app I trap for error 2501 in a report's calling code just in
case there are no records to return (set cancel = True in the report's No
Data event). This doesn't seem to work in my A2k3 version of the same app.
I know I'm missing something simple here but my brain's gone home already.
Anyone help?

Thanks - Keith.

[Allen Browne]

It should work fine in A2003, Keith, so there must be another factor.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Keith Wilby" <he**@there.com> wrote in message
news:43********@glkas0286.greenlnk.net...

In an old A97 app I trap for error 2501 in a report's calling code just in
case there are no records to return (set cancel = True in the report's No
Data event). This doesn't seem to work in my A2k3 version of the same
app. I know I'm missing something simple here but my brain's gone home
already. Anyone help?

Thanks - Keith.

[Keith Wilby]

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

It should work fine in A2003, Keith, so there must be another factor.

Hi Allen,

I've got this in the No Data event of the report:

MsgBox "No items matching criteria.", vbInformation, gcApplication
Cancel = True

and this in the Click event of a command button on a form (simplified):

On Error GoTo errTrap

DoCmd.OpenReport Forms(gcFrmPrint).lstReport.Column(1), acViewPreview, ,
strFilter

' Hide dialog
Me.Visible = False

Exit Sub

errTrap:
If Err.Number <> 2501 Then
Call libErrorHandler(Me.Name, cProcedure)
End If

The other code just sets up filter criteria for strFilter. I could have
sworn this worked in A97, any more thoughts?

Keith.

[Allen Browne]

That looks pretty standard, Keith.

I always use a Resume in the errTrap section instead of just letting it fall
out of the proc.

How about setting a breakpoint (F9), and single-stepping through the code to
see:
a) if another error is occurring, or
b) if err 2501 is occuring somewhere else (such as in libErrHander.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Keith Wilby" <he**@there.com> wrote in message
news:43**********@glkas0286.greenlnk.net...

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

It should work fine in A2003, Keith, so there must be another factor.

Hi Allen,

I've got this in the No Data event of the report:

MsgBox "No items matching criteria.", vbInformation, gcApplication
Cancel = True

and this in the Click event of a command button on a form (simplified):

On Error GoTo errTrap

DoCmd.OpenReport Forms(gcFrmPrint).lstReport.Column(1), acViewPreview, ,
strFilter

' Hide dialog
Me.Visible = False

Exit Sub

errTrap:
If Err.Number <> 2501 Then
Call libErrorHandler(Me.Name, cProcedure)
End If

The other code just sets up filter criteria for strFilter. I could have
sworn this worked in A97, any more thoughts?

Keith.

[Keith Wilby]

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

That looks pretty standard, Keith.

I always use a Resume in the errTrap section instead of just letting it
fall out of the proc.

How about setting a breakpoint (F9), and single-stepping through the code
to see:
a) if another error is occurring, or
b) if err 2501 is occuring somewhere else (such as in libErrHander.)

Thanks Allen, I still can't understand why it's suddenly stopped working, I
haven't changed anything. This is going to turn out to be something really
daft!

Keith.

[Keith Wilby]

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

That looks pretty standard, Keith.

I always use a Resume in the errTrap section instead of just letting it
fall out of the proc.

How about setting a breakpoint (F9), and single-stepping through the code
to see:
a) if another error is occurring, or
b) if err 2501 is occuring somewhere else (such as in libErrHander.)

I've just created a very simple mdb file with one table, one form and one
report. On the form is a command button with

On Error GoTo Err_Trap
DoCmd.OpenReport "Report1", acViewPreview, , "[Text1] = 'qwerty'"

Err_Trap:
If err.Number = 2501 Then MsgBox "barf!"

in the click event and "cancel = true" in the report's No Data event, and
*still* the error isn't trapped. Could it be my installation of Access
playing up (clutching at straws now)?

Keith.

[Keith Wilby]

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

That looks pretty standard, Keith.

I always use a Resume in the errTrap section instead of just letting it
fall out of the proc.

How about setting a breakpoint (F9), and single-stepping through the code
to see:
a) if another error is occurring, or
b) if err 2501 is occuring somewhere else (such as in libErrHander.)

Well I said it was going to be something daft and it is! In the code
options the "break on all errors" option was selected. I changed it to
"break on unhandled errors" and the error is now trapped. I'm not entirely
sure I understand the difference between the options, can you point me at
any documentation? Thanks for your patience.

Keith.

[Bob Quintal]

"Keith Wilby" <he**@there.com> wrote in
news:43********@glkas0286.greenlnk.net:

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43e2a64d$0$31213$5a62ac22@per-qv1-newsreader- 01.iinet.net. au...

That looks pretty standard, Keith.

I always use a Resume in the errTrap section instead of just
letting it fall out of the proc.

How about setting a breakpoint (F9), and single-stepping
through the code to see:
a) if another error is occurring, or
b) if err 2501 is occuring somewhere else (such as in
libErrHander.)

Well I said it was going to be something daft and it is! In
the code options the "break on all errors" option was
selected. I changed it to "break on unhandled errors" and the
error is now trapped. I'm not entirely sure I understand the
difference between the options, can you point me at any
documentation? Thanks for your patience.

Keith.

I don't know of good documantation. However

the "Break on all Errors" option is there to help debug an
application which has error handlers built in, "Break on all
errors" disables all error handling, so you wind up in debug
mode when a error does crop up, without having to comment out or
modify code.

Personally, I'd like it to be non-persistent, because I
sometimes forget to reset it to the correct

--
Bob Quintal

PA is y I've altered my email address.