Understanding an Error number

  • Thread starter Thread starter Victoria
  • Start date Start date
V

Victoria

hello

I have a form with two cbo's that must both have values. When one or both
cbo's and blank, I get erro number -2147352567. I use this in my Error
Handling to open a message box for the user. All of this works perfectly.

Here's my question. This error number doesn't look at all like the 'usual'
4 digit positive number of other errors. What gives? For my own interest,
how would I convert this to a 'typical' error code?
 
On Sun, 8 Feb 2009 15:03:09 -0800, Victoria

In your error handler you can still use Err.Description to get a
somewhat descriptive text.

?hex$(-2147352567)
80020009
That's already a bit easier to read. Typically such values are used by
ADO and other COM object libraries.

If you put 0x80020009 in a search engine you will get several hits.
The "0x" prefix is how C-style languages indicate a hex value.

-Tom.
Microsoft Access MVP
 
The error's description is "You tried to assign the Null value to a variable
that is not a Variant data type.". I believe this is normally error number
3162. I just don't see why Access gave it a large negative error number of
-2147352567.

just wondering!
 
Back
Top