BUG: Drag-Drop Event Procedure Gives Incorrect Error

Last reviewed: July 14, 1997
Article ID: Q154818
The information in this article applies to:
  • Professional and Enterprise Editions of Microsoft Visual Basic, 16-bit only, for Windows, version 4.0

SYMPTOMS

The error "Event procedure does not match description of event having the same name" is generated on a drag-drop event of a control.

WORKAROUND

Install the Visual Basic environment to a local drive. The compiled applications may be installed to a network drive.

STATUS

Microsoft has confirmed this to be a issue in the products mentioned above. We are researching this issue and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

This error occurs in the Visual Basic design environment when Visual Basic has been installed on a network server. Network installation of the Visual Basic environment is not supported, as discussed in the Microsoft Knowledge Base article referenced below. Other errors have also been noted but the error described here appears to be a consistent indicator.

Steps to Reproduce Problem

Install the 16-Bit Edition of Visual Basic 4.0 onto a network server. Load the Mouse.VBP sample project located in the \VB\SAMPLES\MOUSE directory. The error may then be reproduced by compiling the project into an EXE file or running the program with the "compile on demand" option disabled.

REFERENCES

For more information, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q142517
   TITLE     : VB Doesn't Support Administrator or Network Installation
 

	
	


Keywords : EnvtDes kbsetup Setins vb416 vb4win
Version : 4.0
Platform : NT WINDOWS
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.