Error handling question

If I have a command button for SendObject that opens an e-mail, and if I
then click the X at the top right of the e-mail without sending it, I will
get an Error 2501 (the Send Object action was canceled, or something like
that) message if I do not trap the error.

"Rick Brandt" wrote in message
t...
BruceM wrote:
There may be a blank message before this one. I think I clicked the
Send button too soon.

Thanks for responding. I like the idea of the custom function, since
I often need to trap Error 2501, but I'm not quite certain how to
make it work. If I have a command button for SendObject (to send an
e-mail, for instance), and if the user decides against sending the
e-mail, how do I trap that when opening the form? Would I make a
function to trap 2501, then call the function in place of the If ...
End If part of the ProcErr code? Or am I missing your point?

Not sure I understand the question. If you are pressing a button that
calls
SendObject what does that have to do with opening a form?

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Thanks, Rick!


Fred

"Rick Brandt" wrote in message
t...
Fred Boer wrote:
Dear Rick:

Any chance you might share those functions?

Pretty basic stuff really (once you see them I'm sure you'll agree).

The one for the report adds an option for Fit-To-Window, You will have to
replace my custom ErrorMessages function with whatever you normally use
for
displaying error messages.


'Wrapper for DoCmd.OpenForm that ignores error 2501
'*******************************************
Public Function fnOpenForm(stFormName As String, _
Optional lngView As Long =
acNormal, _
Optional stFilterName As
String, _
Optional stWhereCondition As
String, _
Optional lngDataMode As Long =
acFormPropertySettings, _
Optional lngWindowMode As Long
= acNormal, _
Optional stOpenArgs As String)
As Boolean

On Error GoTo ErrHandler

DoCmd.OpenForm stFormName, lngView, stFilterName, stWhereCondition,
lngDataMode, lngWindowMode, stOpenArgs
fnOpenForm = IsLoaded(stFormName)

Egress:
Exit Function

ErrHandler:
Select Case Err.Number
Case 2501
'ignore
Case Else
ErrorMessages "fnOpenForm Function"
End Select
Resume Egress
End Function

'Wrapper for DoCmd.OpenReport that ignores error 2501
'*********************************************
Public Function fnOpenReport(stReportName As String, _
Optional lngView As Long =
acViewNormal, _
Optional stFilterName As
String, _
Optional stWhereCondition As
String, _
Optional FitToWindow As
Boolean) As Boolean

On Error GoTo ErrHandler

DoCmd.OpenReport stReportName, lngView, stFilterName, stWhereCondition
fnOpenReport = IsRptLoaded(stReportName)
If FitToWindow = True Then DoCmd.RunCommand acCmdFitToWindow

Egress:
Exit Function

ErrHandler:
Select Case Err.Number
Case 2501, 2046
'ignore
Case Else
ErrorMessages "fnOpenReport Function"
End Select
Resume Egress
End Function


--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

BruceM wrote:
If I have a command button for SendObject that opens an e-mail, and
if I then click the X at the top right of the e-mail without sending
it, I will get an Error 2501 (the Send Object action was canceled, or
something like that) message if I do not trap the error.

Then the code that calls SendObject has to trap for Error 2501 and ignore it
(or whatever else you want to do when that happens).

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Thanks, that was what I figured. I have been doing that, but as I said, I
keep writing the same lines of error message and error handling code (msgbox
"Error #" ... etc.) for each event. I had hoped there was a way to avoid
the redundancy. I suspect not. It is not a big deal. I appreciate the
time you have put into the replies.

"Rick Brandt" wrote in message
. ..
BruceM wrote:
If I have a command button for SendObject that opens an e-mail, and
if I then click the X at the top right of the e-mail without sending
it, I will get an Error 2501 (the Send Object action was canceled, or
something like that) message if I do not trap the error.

Then the code that calls SendObject has to trap for Error 2501 and ignore
it
(or whatever else you want to do when that happens).

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

BruceM wrote:
Thanks, that was what I figured. I have been doing that, but as I
said, I keep writing the same lines of error message and error
handling code (msgbox "Error #" ... etc.) for each event. I had
hoped there was a way to avoid the redundancy. I suspect not. It is
not a big deal. I appreciate the time you have put into the replies.

Just as I did with functions for OpenForm and OpenReport you could create a
custom "wrapper function" that you use instead of SendObject. Within that
function you still use SendObject passing it all of the arguments that your
wrapper function uses and then you write the erorr handler in your custom
function that ignores error 2501.

Now you just use the wrapper function instead of SendObject directly and no
longer need to keep writing the error handler over and over again.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

I can see where that technique could come in handy, and not just with
SendObject. I need to learn to look for opportunities to eliminate some of
the repetition that is inevitable with code. Thanks for pointing me in that
direction, and thanks too for all of your comments and suggestions on this
topic.

"Rick Brandt" wrote in message
...
BruceM wrote:
Thanks, that was what I figured. I have been doing that, but as I
said, I keep writing the same lines of error message and error
handling code (msgbox "Error #" ... etc.) for each event. I had
hoped there was a way to avoid the redundancy. I suspect not. It is
not a big deal. I appreciate the time you have put into the replies.

Just as I did with functions for OpenForm and OpenReport you could create
a
custom "wrapper function" that you use instead of SendObject. Within that
function you still use SendObject passing it all of the arguments that
your
wrapper function uses and then you write the erorr handler in your custom
function that ignores error 2501.

Now you just use the wrapper function instead of SendObject directly and
no
longer need to keep writing the error handler over and over again.

--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com