HOWTO: Expedite the Visual Basic Support Process

ID: Q188586

The information in this article applies to:
  • Microsoft Visual Basic Learning, Professional, and Enterprise Editions for Windows, versions 5.0, 6.0
  • Microsoft Visual Basic Standard, Professional, and Enterprise Editions, 16-bit and 32-bit, for Windows, version 4.0

SUMMARY

This article provides tips on how to reduce your Visual Basic program to a minimum so you can accurately describe the problem to a support professional, who will look for a way to duplicate the problem using the least objects and code.

When you encounter a problem with a Visual Basic program and have to call Microsoft Technical Support for assistance, you can reduce your call time prior to calling by creating a version of your program that contains only those pieces needed to reproduce the problem.


MORE INFORMATION

The following is the basic strategy of creating a minimal Visual Basic program to isolate the problem so a support professional can find a solution quickly.

  1. Make a back-up copy of your program.


  2. Follow the steps shown in the next section. After completing each step, check to see if the problem still exists.


  3. When you have finished, copy the minimal program to a new project and check to see if the problem still exists.


NOTE: You may not have to perform all the steps presented here to isolate your problem. However, you may need to modify your code to get the program to compile properly to reproduce the problem.

Steps to Reduce Your Program to a Minimum

  1. Identify and remove all forms, code modules, class modules, user controls, and property pages not needed to re-create the problem.


  2. From the remaining forms, remove all controls and referenced objects not needed to re-create the problem.


  3. From the Project menu, clear all References and Components not needed to re-create the problem.

    NOTE: Visual Basic prevents any control or reference used by the program from being removed.


  4. Remove all unexecuted code from the remaining forms.


  5. At this point, you may be able to remove additional controls that are not used by the remaining forms.

    NOTE: Try clearing additional References and Components, as described in step 3.


  6. Remove pieces of code from the remaining procedures that do not appear to be related to the problem.


  7. Try to remove pieces from the original project. For example, if the problem is related to database access, use another database to reproduce the problem, such as BIBLIO.MDB that ships with Visual Basic.


  8. Repeat this process until you have the smallest possible program, then copy this program to a new project.


Additional query words: kbDSupport kbdss kbVBp500 kbVBp400 kbVBp kbVBp600

Keywords : kbGrpVB
Version : WINDOWS:4.0,5.0,6.0
Platform : WINDOWS
Issue type : kbhowto


Last Reviewed: January 5, 2000
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.