Err.Raise 40040 Bug from MS

BUG: Err.Raise 40040 Stores the Err.Number as 440

SYMPTOMS
When the statement Err.Raise 40040 is executed, the value of Err.Number is set to 440.

RESOLUTION
Do not use the user defined error 40040.

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION
If you raise the error code 40040 (=&H9C68) using the Err.Raise method, Visual Basic sets the value of Err.Number to 440. The Err.Description and other properties of the Err object are set correctly.

Steps to Reproduce Behavior
1. Create a Visual Basic Standard EXE project. Form1 is created by default.
2. Paste the following code in the General Declarations section of Form1:

VB Code:

Private Sub Form_Load()
   On Error Resume Next
   Err.Raise 40040
   MsgBox Err.Number & ": " & Err.Description ' will display 440
   Err.Clear ' Clear the error for the next Raise method
   Err.Raise 440
   MsgBox Err.Number & ": " & Err.Description
End Sub

3. Run the program. A message box with the error number and description raised for 40040 will be displayed.
4. Click OK and a message box with the error number and description raised for 440 will be displayed.

APPLIES TO
• Microsoft Visual Basic 5.0 Learning Edition
• Microsoft Visual Basic 6.0 Learning Edition
• Microsoft Visual Basic 5.0 Professional Edition
• Microsoft Visual Basic 6.0 Professional Edition
• Microsoft Visual Basic 5.0 Enterprise Edition
• Microsoft Visual Basic 6.0 Enterprise Edition

Keywords: kbbug KB216547

URL: http://support.microsoft.com/default...b;en-us;216547

Thanks,


Can you rub my back now?

Scientists have determined that all potatoes today originated from a "mother" potato species in Peru about 7000 years ago. The Adam and Eve of all potatoes.

http://uk.news.yahoo.com/04102005/34...-potatoes.html

Quote:

---

Originally Posted by NoteMe

Thanks,


Can you rub my back now?

---

::rubs noteme's back::

I searched, but couldn't find the original question: Q216547

Quote:

---

Originally Posted by dglienna

I searched, but couldn't find the original question: Q216547

---

I went to MSDN KB and was looking for a list of error codes but of course did not find any, then found this article and thought I should post it here. Just in case anyone didn't know -- I know I didn't.

Wigii woggodee DOOOOOOOO

Was it dated April 1, by any chance?

Quote:

---

Originally Posted by dglienna

Was it dated April 1, by any chance?

---

Article ID : 216547
Last Review : May 12, 2003
Revision : 1.0

No, it was definately dated April 1.

Quote:

---

Originally Posted by programmer_boy

No, it was definately dated April 1.

---

Didnt find that date anywhere on the article.

Shouldn't this thread be in the General PC or Classic VB forums? Then it may be taken a bit seriously...

Wajawoo blaerad eoch

Quote:

---

Originally Posted by Valleysboy1978

Wajawoo blaerad eoch

---

Who told you that? It's a lie!

Bluteow nah sertars walalala

Ewoa hebrezieos aasket afja!

Wakar nah chearwa eh mweat arr naratai

Ekky-ekky-ekky-ekky-z'Bang, zoom-Boing, z'nourrrwringmm.

You must find me a shrubbery!

Quote:

---

Originally Posted by mendhak

Ekky-ekky-ekky-ekky-z'Bang, zoom-Boing, z'nourrrwringmm.

You must find me a shrubbery!

---

Are you a knight who, until recently, said Ni!?