Visual Basic Q&A

Symptoms
A data control causes an application error at runtime if the data controlcontains with a blank RecordSource property at design time and theUpdateControls method is executed. The application error ends Visual Basic.
Resolution
To work around this bug, at design time, set the data control’sDatabaseName property to a database and the RecordSource property to atable in the database. Other controls that are bound to the data control,such as a text box, should also have a value in the control’s DataSourceproperty

Symptoms
Unloading a form with a DBGrid control by using the Unload statement in theany event of the DBGrid control causes an application error that ends theVisual Basic program.The following are ways to work around this issue:
Set the form to nothing prior to unloading the form.
-or-Unload the form in an event other than a DBGrid event.
Resolution
Microsoft has confirmed this to be an issue in the Microsoft productslisted at the beginning of this article. Microsoft is researching thisproblem and will post new information here in the Microsoft Knowledge Baseas it becomes available.

Symptoms
Closing a maximized code window after performing a Find and Find Nextsubsequently on the code window causes Visual Basic to crash.
The possible error messages are:

An application error has occurred.
VB6.exe
Exception: Access Violation (0×00000005) Address: 0×0fb16e90
-or-

An application error has occurred.
VB5.exe
Exception: Access Violation (0×00000005) Address: 0×0fb16e90
-or-

This program has performed an illegal operation and will be shut down.
-or-

Edit: VB6.EXE Application Error
The instruction at “0×0fa76bb1″ referenced memory at “0×00000058″. The
memory could not be “read”.
-or-

Edit: VB5.EXE Application Error
The instruction at “0×0fa76bb1″ referenced memory at “0×00000058″. The
memory could not be “read”.
Resolution
This problem does not occur if the code window is not maximized.