INFO: Routing Issues for Windows CE Toolkit for Visual Basic

Last reviewed: February 4, 1999
Article ID: Q181038

The information in this article applies to:
  • Microsoft Windows CE Toolkit for Visual Basic 5.0
  • Microsoft Windows CE Toolkit for Visual Basic 6.0

SUMMARY

This article is intended to help identify issues that should be routed to the "DSB VBCE" Compass queue. The full name for the products are "Windows CE Toolkit for Visual Basic 5.0," referred to as VBCE5 or "Windows CE Toolkit for Visual Basic 6.0," referred to as VBCE6. Alternately, either product could be referred to as simply "VBCE".

The following is a list of words that the customer may say that will help identify VBCE issues. (If you find any additional unique words or phrases that customers use to identify the product as VBCE, be sure to add a comment to this article.) 

   VBCE              Embedded           Emulator
   Device            Debugger           Synchronize
   HPC               Handheld           Windows CE
   WinCE             Toolkit            Control Manager
   Heap Walker       .pvb file          .vb file
Also, three of the most common VBCE errors are:

Application Error: 

   An Error was encountered while running this program.
Application Error: 

   Error while attempting to load the Startup Form.
Microsoft Visual Basic: 

   Copying required files to the remote device failed!
These three errors are unique to VBCE and easily identify the product as such.

If you are not sure that the customer is using VBCE, ask the question "Are you using the Windows CE Toolkit for Visual Basic 5.0 or or Visual Basic 6.0?"

If the product is the Windows CE Toolkit for Visual Basic 5.0 or or Visual Basic 6.0, please gather the following additional information for the case:

  • Which version of the product is being used?
  • What is the exact error message the customer is receiving?
  • What is the customer doing when the error message occurs (running, compiling, installing, etc)?
  • What development operating system is the customer using?
  • Does the problem occur in the emulator, on the device, or both?
  • If the problem occurs on the device, what brand of device does the customer have and/or what processor does the device have (MIPS or SH3)?
  • Is the customer using any ActiveX controls in the project? If so, did they use the Control Manager to install the controls into the emulator or device?
  • Has the customer searched the Visual Basic section of the Knowledge Base for the phrase "Windows CE"?
  • Is the customer using any other add-ins besides the VBCE add-in? If so, which ones?

(c) Microsoft Corporation 1999, All Rights Reserved. Contributions by Mike Dixon, Microsoft Corporation

Additional query words:

Keywords : kbWinCE100 kbVBp500 kbVBp600 kbToolKit kbGrpVB
Version : WINDOWS:
Platform : WINDOWS
Issue type : kbinfo

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: February 4, 1999
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.