Visual Basic Q&A

Symptoms
Clicking the plus sign to expand a stored procedure in the Data View window in either Visual Basic, Visual InterDev, or Visual J++ generates the following error message if the stored procedure contains calls to extended stored procedures that return something other than 0 or 1, such as xp_cmdshell:

Devenv.exe – Application ErrorThe instruction at “0×412406f3″ referenced memory at “0×00000006″. The memory could not be “read”.
Resolution
Clicking the plus sign executes the stored procedure to enumerate the parameters and tables for the stored procedure. When the data environment tries to execute xp_cmdshell it generates an error.
NOTE: This problem does not occur with SQL Server 7.0 or later. It also does not occur under a Microsoft Windows 2000 environment.

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.