Ugg Boots Sale Charms Pandora Korut pandora uk rs gold cheap ghd straighteners tiffany bangles thomas sabo armbanden links of london earrings cheap mbt levis jeans men replica chanel sale vivienne westwood kaulakorut pandora jewellery

Current List of VB6 Bugs and Issues

Yes, I know it is hard to believe that there would be bugs or issues with VB6 already. Here is our initial list of them.

IDE Bugs

Bug Name Bug Description LinkReported By
Font in Data View window changes to match the SQL Editor Steps to reproduce the problem:
  1. Set your font for the code to a different size.
  2. Open the SQL Editor from the Data View window.
    3. The font in the SQL Editor is nicely enlarged to the code size you specified.
  3. Look at the Data View window. It also made itself the new size, making it difficult to read the contents if you made the font large.
 None Deborah Kurata
VERY MINOR: Pop up menu for the Related Documents provides a Properties option, that does not do anything. Also, resource files have a Save As option, but it does not do anything. Steps to reproduce the problem:
  1. Right click on a file in the Related Documents.
  2. Select Properties. Nothing happens
  3. Right click on a resource file.
  4. Select Save As. Nothing happens. For most other Related Documents, Save As is gray.
 None Deborah Kurata
MINOR: In the Customize dialog box to customize the menus, the Description and "?" buttons don't do anything Steps to reproduce the problem:
  1. Right click on the menu.
  2. Select Customize.
  3. Click on the "?" button, it does nothing.
  4. Click on the Commands tab.
  5. Click on the Description button, it does nothing.
 None Ron Schwarz
Form Layout window does not display the opened windows If the Form Layout window is closed when no forms exist and you exit VB, the Form Layout window won't display any forms when the Form Layout window is reopened upon subsequent use. Steps to reproduce the problem:
  1. Enter VB.
  2. Remove the default form.
  3. Close the Form Layout window.
  4. Exit VB.
  5. Enter VB.
  6. View Form Layout window. No forms appear in the Form Layout window.
  7. Exit VB again.
  8. Enter VB again.
  9. Forms now appear in the Form Layout window.
 None Deborah Kurata
Properties of the Err object are not checked at compile time. Steps to reproduce the problem in the VB6 IDE:
  1. Add a list of code: Debug.Print Err.Desription (notice the misspelling)
  2. Compile the application. You will not receive a syntax error
  3. Run the application. You will get a "Method or data member not found error when the line of code is executed.
 None Deborah Kurata

ActiveX Bugs

Bug Name Bug Description LinkReported By

Form and Control Bugs

Bug Name Bug Description LinkReported By
Unloading an MDI parent from an MDI child locks up the application. To reproduce:
  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.
 Craig Clearman

Data Access Bugs

Bug Name Bug Description LinkReported By
The Access OLE-DB driver does not work the first time when used with fields tied to a Data Environment Steps to reproduce the problem:
  1. Use the Data Environment (DE) and connect to a database using the Access OLE-DB driver.
  2. Build a hierarchical recordset.
  3. Drag the parent hierarchical recordset from the DE to a form. Appropriate controls will appear.
  4. Run the project - the fields are not populated.
  5. Change the DE to use the ODBC driver and run again, it works!
  6. Change the DE back to the Access OLE-DB driver. Now that works too!
 None Deborah Kurata
Cannot bind to a date field if there are no records in the recordset. You can bind a date control on a form by setting the DataSource to a recordset and the DataField to a date field. However, if the recordset is empty it generates and error and will not perform the binding. NOTE: This behavior was only test using Access. None Deborah Kurata
MSChrt20.OCX ignores the first row of a recordset. MSChrt20.OCX throws out the first row of a Recordset. For instance, if you have a Recordset with a calendar year’s worth of monthly data, the chart shows only February - December.

The work-around is to explicitly move the recordset's record point, e.g. execute a MoveFirst. 		None Roger Jennings
MSChrt20.OCX does not correct react to null values. If the Recordset acting as the bound graph’s DataSource contains a null value, which is common for Jet crosstab queries, no data points appear after the null is encountered. You have to fix the Recordset, which means saving it, then opening it from the saved file, in order to make it updateable. Replace the nulls with zeroes, then Set Chart.DataSource = Recordset. None Roger Jennings

Other Bugs

Bug Name Bug Description LinkReported By
The Class Builder utility Enum builder does not allow equations. A common use of Enums is for defining errors of the form: vbObjectError + 512 + 100. You cannot put these types of statements into the Class Builder utility Enum builder. None Deborah Kurata
The Class Builder utility does not correctly build Property procedures for properties defined of an enumerated type. The Class Builder utility now allows you to define properties to be of an enumerated data type. However, if you use this feature, the Property Get code is generated incorrectly by the Class Builder utility. For example: 
Public Property Get TestProperty() As TestEnum
	Set TestProperty = mvarTestProperty
End Property


Notice the "Set" key word. This generates a syntax error. 		None Deborah Kurata

"Features"

Feature Name Feature Description LinkReported By
A public member of a class does not behave like a public member of a standard module If you pass a public variable from a standard module to a routine that increments that value, the value will be incremented. If you pass a public variable from a class, it will not be incremented.

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. 		Sample Code Patrick Steele as seen in dejanews

Revised: July 16, 2004.