How do I troubleshoot Visual Basic* applications that don't run after installation?
Have you ever had a Visual Basic application that failed to run after installation? This generally occurs because of missing dependency files or improperly registered files. Visual Basic applications are dependent on .dll and .ocx files to run properly. When these dependent files are missing or are improperly registered, the Visual Basic application does not run. Use Wise Visual Basic Import Wizard as a springboard to create your application. The Wise Visual Basic Import Wizard reads a Visual Basic project file and imports all of the files referenced by the Visual Basic project. The Visual Basic Import Wizard also checks for file dependencies in corresponding .dep files and adds those dependencies to the installation script. If the Visual Basic project file is not complete or there is not a .dep file associated with a file that has dependencies, then the installation might be missing files required for the application to run successfully. This article explains the three most common troubleshooting steps you should take whenever your Visual Basic application does not run properly.
To troubleshoot your Visual Basic installation:
Missing dependency files or improperly registered files in your application often cause errors when an installation is complete. Apply the troubleshooting tips in this article to decrease the time you spend debugging the application and increase the likelihood that every installation of your application runs successfully.