Article ID: 129446
Article Last Modified on 12/9/2003
APPLIES TO
- Microsoft Visual Basic 4.0 Standard Edition
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 4.0 16-bit Enterprise Edition
- Microsoft Visual Basic 4.0 32-Bit Enterprise Edition
This article was previously published under Q129446
SYMPTOMS
Visual Basic version 4.0 generates a compile error if there are two Declare statements with the same name in the project when the Declare statement takes a UDT (User Defined Type) or object as a parameter. However, there is no problem if none of the parameters are UDTs or Objects.
RESOLUTION
Put the Private keyword in front of one of the Declare statements.
STATUS
This behaviour is by design. This behavior was allowed in Visual Basic version 3.0, but is no longer allowed in Visual Basic version 4.0.
MORE INFORMATION
Steps to Reproduce Behavior
- Start a new project in Visual Basic. Form1 is created by default.
- Add two new Modules (Module1 and Module2) by choosing Module from the Insert menu.
Add the following code to the General Declarations section of Module1:
Type POINT X As Long Y As Long End Type Declare Sub GetCursorPos Lib "user32" (lpPoint As POINT)Add the following code to the General Declarations section of Module2:
Declare Sub GetCursorPos Lib "user32" (lpPoint As POINT)In the Form_Click event for Form1, add the following code:
Dim pt As POINT GetCursorPos pt Print pt.X, pt.Y- Choose Make EXE File from the File menu to compile the program. You will receive the error, "Ambiguous Name Detected: GetCursorPos."
Additional query words: incompatibility 4.00 vb4win vb4all
Keywords: kbprb KB129446
