Attention: Access Junkie

T

Tom Wickerath

Hi Jeff,

Okay, I'm curious about an answer you provided on 8/13:

Subject: Re: Access Runtime Error Number: 0

Both you and Norman had similar answers that included the use of the Hex function in the message
box statement. While this was also present in the original poster's code, I'm curious as to why
you included it in your answer back:

MsgBox "Error number: " & Hex(Err.Number)

It seems to me that this just helps obfuscate the true error. For example, "Error 13: Type
mismatch" becomes "Error D: Type mismatch". How does this help to clarify the situation....


Tom
 
N

Norman Yuan

A clarification:

The "Hex(Err.Number)" part is from original post. Jeff and I just simply
copied that part to our answers. We just focus on direct answer to the
poster's question and did not pay attention to the "Hex()" thing. I'd be
curious to to ask the original poster: what i sthe purpose to "Hex" the
error number?
 
J

Jeff Conrad

Hi Tom,

As Norman already mentioned, we both just used the original poster's error handling code in our
responses. Probably a bad assumption on my part that the Hex function actually gave a 'meaningful'
error!
:)

To be totally honest I actually thought the Hex thing was some custom error handling function that
the poster had created since I had never heard of it before! I use a generic handling code for most
things, but a more complicated custom error handling routine for more advanced stuff. I assumed it
was something the poster had created. Bad Jeff!
 
T

Tom Wickerath

Hi Jeff and Norman,

Thanks for your responses. I was wondering if there was some advantage to returning the Hex
representation of an error code, since it was shown that way in both answers. However, I couldn't
figure out what that advantage might be; my curiousity finally got the better of me and I thought
I'd ask.

By the way, Jeff, I meant to say "good job" on your recent post: "Top 10 Reasons Why MVP Cheryl
Fischer Is Going To Heaven And Will Be Missed".

Tom
_____________________________________


Hi Tom,

As Norman already mentioned, we both just used the original poster's error handling code in our
responses. Probably a bad assumption on my part that the Hex function actually gave a
'meaningful'
error!
:)

To be totally honest I actually thought the Hex thing was some custom error handling function
that
the poster had created since I had never heard of it before! I use a generic handling code for
most
things, but a more complicated custom error handling routine for more advanced stuff. I assumed
it
was something the poster had created. Bad Jeff!

--
Jeff Conrad
Access Junkie
Bend, Oregon
_____________________________________


Hi Jeff,

Okay, I'm curious about an answer you provided on 8/13:

Subject: Re: Access Runtime Error Number: 0

Both you and Norman had similar answers that included the use of the Hex function in the message
box statement. While this was also present in the original poster's code, I'm curious as to why
you included it in your answer back:

MsgBox "Error number: " & Hex(Err.Number)

It seems to me that this just helps obfuscate the true error. For example, "Error 13: Type
mismatch" becomes "Error D: Type mismatch". How does this help to clarify the situation....


Tom
 
J

Jeff Conrad

Hi Tom,
Thanks for your responses. I was wondering if there was some advantage to returning the Hex
representation of an error code, since it was shown that way in both answers. However, I couldn't
figure out what that advantage might be; my curiosity finally got the better of me and I thought
I'd ask.
Click to expand...

No harm in asking, we both learned something!
That is what this place is for after all.
By the way, Jeff, I meant to say "good job" on your recent post: "Top 10 Reasons Why MVP Cheryl
Fischer Is Going To Heaven And Will Be Missed".
Click to expand...

That is one list I surely did not want to make.
:-((
I have fun making the other lists, but that one was extremely difficult to make for personal
reasons.
 
Top