FIX: Calling Method in User Ctrl w/ParamArray Causes Fatal Exception During Compile
ID: Q221225
|
The information in this article applies to:
-
Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 6.0
SYMPTOMS
If no parameter is passed, a fatal exception occurs in Visual Basic 6.0 when you compile a project that calls a method in a user control with a ParamArray parameter.
RESOLUTION
There is no workaround available for this problem. You must pass at least one parameter to avoid it.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
This bug was corrected in Visual Studio 6.0 Service Pack 3.
For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:
Q194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why
Q194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed
MORE INFORMATION
Steps to Reproduce Behavior
- Start a new ActiveX control project.
- Add the following method:
Option Explicit
Public Function PassVararg (ParamArray t() As Variant) As Long
End Function
- Compile the user control.
- Start a new Standard EXE Project. Form1 is created by default.
- Make a reference to the user control that you just created.
- Place an instance of the user control on Form1.
- Change the name of the user control to Ocx1.
- In Form_Load event procedure, add the following code:
Dim k as Long
k = Ocx1.PassVararg
- Save the project.
- Compile the project.
RESULT: A fatal exception occurs. This problem only occurs in an ActiveX control project. It does not happen in an ActiveX DLL project.
Additional query words:
Keywords : kbservicepack kbActiveX kbCtrlCreate kbVBp600bug kbGrpVB kbVS600sp2 kbVS600SP1 kbVS600sp3fix
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbbug