KB Article ID: Q167123

KB Article ID: Q167951

To fix invalid command bar references in the registry, exit VB and then:

1.Start Regedit.exe.
2.Delete the following key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Visual Basic\5.0

3.Close Regedit.
4.Restart Visual Basic.

1. Create the custom toolbar with the horizontal alignment button on it.
2. Create a new project.
3. Put two text boxes on the form.
4. Select both text boxes.
5. Press the F4 key.
6. CRASH!

In VB5 IDE, do:
1) Project | Properties.
2) Select the tab "Make".
3) In the field "Command line arguments" type more than 255 chars.
4) Press OK.
5) Again do Project | Properties
6) Look that the "Command line arguments" field, it has been truncated at 255 chars.

In the VB5 IDE, do:
1) Open a new EXE Project
2) On the default form, add a command button (or any controls)
3) DblClick the button, add some code.
4) Open the Properties window for the Form, Change MDIChild to TRUE
5) Save the form, project file.
6) Open Layout Window.
7) Right-click on the form image in the layout window and set StartupPosition to Center Owner. (Or anything except Manual).
8) Save
9) Close the form
10) Open the form. You will get "Invalid Property". Click OK. Controls are gone.

NOTE: If you close VB immediately after saving the form, the invalid property is saved in the FRM file. However, when you open VB again, you get an error message, but the controls are all there.

In VB5 IDE, do:
1) Right click on the menu.
2) Select Customize.
3) Click on the "?" button, it does nothing.
4) Click on the Commands tabe.
5) Click on the Description button, it does nothing.

1. Create an ActiveX DLL.
2. Add a standard EXE to the project group to test the DLL.
3. Add a reference in the standard EXE to the DLL.
4. Compile the DLL.
5. Remove the DLL from the group. This resets the reference from the ActiveX DLL project to the DLL itself.
6. Test again. Things should be fine.
7. Re-add the DLL to the project group.
8. Recompile the DLL. You will now get this error.

The work around is reset the reference from the ActiveX DLL (.dll) to the ActiveX DLL project (.vbp) and then recompile.

KB Article ID: Q167122

KB Article ID: Q168155

1. Add an MDI parent form to a sample application.
2. Set form1 MDIChild property to True.
3. In the Form_Unload event for the MDI child application, add the following line of code: Unload MDIForm1.
4. Run the application. It will hang.

1. Use the PanEuro version of Windows 95.
2. Add two text boxes.
3. Set the maxLength property to 8.
4. Add the following code:
   Private Sub Text1_KeyPress(KeyAscii As Integer)
   If KeyAscii = 13 Then
   SendKeys "{tab}"
   KeyAscii = 0
   End If
   End Sub
5. Run the application, type in 8 characters and press the Enter key. In the US version of Windows this moves the cursor to the next field. In the PanEuro version it beeps and will not move to the next field.

1. Add a list box to a form.
2. Add the following code:
   Private Sub Form_Load()
   Dim i As Long
   For i = 0 To 70000
   List1.AddItem "Item " & i
   Next i
   End Sub
   
   Private Sub List1_Click()
   Me.Caption = "ListIndex: " & List1.ListIndex _
   & "Converted: " & CLng("&H" & Hex(List1.ListIndex))
   End Sub
3. Run the application. The form may take a while to load.
4. Try accessing a number after 32767. The listIndex is invalid but the converted index is correct.
5. Try accessing a number after 65532. Both values are invalid.

KB Article ID: Q168163

KB Article ID: Q168153

KB Article ID: Q168156

KB Article ID: Q168158

KB Article ID: Q168159

KB Article ID: Q168157

KB Article ID: Q168160

KB Article ID: Q168162

KB Article ID: Q168161

KB Article ID: Q167950

To work around this bug, you can use the Format statement around the date value as follows:

Write #1, Format$(rsInvoices!OrderDate)

KB Article ID: Q168850

This is because public variables in a class are treated as if they were property procedures. The value of the property is then passed to the routine instead of the reference to the variable, so the value is not seen as incremented. Download the sample code to see how this works.