PRB: Instantiating a Project-Compatible Server Causes Error 430

• Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, version 6.0

SYMPTOMS

Instantiating a class within a server that has been previously compiled but is now running within the Visual Basic IDE, causes run-time error 430.

CAUSE

When a Visual Basic project is compiled with Project Compatibility, the CLSID remains the same while the IID changes for subsequent builds. Therefore, attempting to create the specific class in the "compatible" server generates the following error because the specific IID has changed and no longer exists:

Run-time error '430':
Class does not support Automation or does not support expected interface

RESOLUTION

Use Binary Compatibility.

STATUS

This behavior is by design.

MORE INFORMATION

Steps to Reproduce Behavior

1. Start a new ActiveX DLL project in Visual Basic. Class1 is created by default.



2. From the Project menu, select Project Properties, and then change the Project Name to SPP2.



3. From the File menu, select Make SPP2.DLL.



4. Add the following code to the code module of Class1:

   
         Private Sub Class_Initialize()
            Debug.Print "Initialize"
         End Sub 




5. Start a second instance of Visual Basic and create a new Standard EXE project. Form1 is created by default.



6. Select References from the Project menu, and add a reference to SPP2.dll.



7. In Form1, place the following code:

   
         Private Sub Form_Load()
            Dim x As SPP2.Class1
            Set x = New Class1
         End Sub 




8. Switch back to the first instance of Visual Basic and run SPP2.



9. Switch back to the second instance of Visual Basic and press the F8 key to step into the code.



10. Continue to press the F8 key until the Error 430 DialogBox pops up.

Additional query words: kbDSupport kbAppSetup kbVBp600 kbdss
kbVBp kbIDE kbActiveX

Keywords : kbGrpVB
Version : WINDOWS:6.0
Platform : WINDOWS
Issue type : kbprb