VB6 Application Compatibility With Vista

Posted on 2008-11-10
Medium Priority
Last Modified: 2013-11-14
I have an application that was written in VB6. This application installs properly (w/o error) on Vista machines. Several months ago I posted a question regarding the "Exe. Has Stppped Working" error that came up when this application was run on Vista and subsequently a compatibility file (.sdb) was created that ran with the installer to set compatibility for "Run As Administartor" and "Windows 2000" compatibility. I do not know why these had to be set as they were but after experimenting with the File>>Properties>>Compatibility this was discovered to make this application run successfully under Vista. (Hence the sdb file was created to set these properties globally during installation. The problem is now the same "Exe. Has Stopped" error is coming up again. Without any indication of why or what other items need to be set in the .sdb file I have no way of knowing what else to do to resolve this. We have essentially eliminated all Vista users from potential sales and this is very damaging to our business. The program is being converted to VB.net but it is 400000 lines of code so this process is taking a long time. We need to get it compatible now. Is there a utility that can be run against an application taht will spell out whrer exactly the incompatibility lies so it can be added to the .sdb? Is there a recommended Installer that would work better? Currently using Installshield 2008 Express. Help!!!
Question by:gcook17

Accepted Solution

bchesley earned 1000 total points
ID: 22923393
You may need to verify that you have the latest and greatest run time distribution files for VB6 - see the following link for details


If this does not get you moving in the right direction you may want to look a little more deeply into how UAC settings affect your program and or run time files and also how Vista implements "virtual store" as a security mechanism.

Good luck.

LVL 57

Assisted Solution

McKnife earned 1000 total points
ID: 22925393
My approaches would be:
-is the .sdb still intact and applied? Reapply it.
-What changed at the vista systems? UNinstall the latest MS updates
-Use a clean Vista system (with SP1) without further updates to check
-Find the reason through monitoring: procmon is freeware by MS to do this. Use its crosshair filtering option. Compare the logfile to that of another windows OS.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Have you ever wanted to restrict the users input in a textbox to numbers, and while doing that make sure that they can't 'cheat' by pasting in non-numeric text? Of course you can do that with code you write yourself but it's tedious and error-prone …
Monitor input from a computer is usually nothing special.  In this instance it prevented anyone from using the computer.  This was a preconfiguration that didn't work.
Get people started with the process of using Access VBA to control Excel using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Excel. Using automation, an Access application can laun…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…
Suggested Courses
Course of the Month13 days, 18 hours left to enroll

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question