loads of runtime errors visual basic app

[RATiO]

Trying to run a vb app on Windows 7 and getting loads of runtime errors. Everytime I sort one another presents itself. Ive installed visual basic 6 runtimes, microsoft jet 3.5. The current runtime error is 335.

What can be done to get those old apps running on Windows 7 Enterprise SP1?

[lars77]

It's been a while since I've messed around with VB6 but hopefully this helps...

Have you already tried running the application in compatibility mode? e.g. Right-click on the program's shortcut, select Properties, click Compatibility & set it to run as a Windows XP program, etc.

Supposedly Win 7 already has the VB6 runtime so you shouldn't have needed to install the VB6 runtime, I think? It's likely the program has other dependencies that may not be compatible with Win 7? This really depends on the program, maybe contact the dev for that info?

Also, if the program is crazy old, you may need to run it with elevated permissions as well as with admin privileges. It is possible that the program wasn't built with a manifest thus won't know about Win Vista/7's UAC.

[RATiO]

It's a work PC so the user doesn't have permission to run apps in compatibility mode. The app ran fine on Windows XP but we've recently upgraded to Windows 7 on the same PC

[lars77]

It's a work PC so the user doesn't have permission to run apps in compatibility mode. The app ran fine on Windows XP but we've recently upgraded to Windows 7 on the same PC

So, have you actually tried running it in compatibility mode, or with elevated & admin privileges? I mean seriously, just try logging in as a user that has those permissions & see what happens. I suspect your legacy app just isn't going to run normally in Win Vista/7 without doing something extra like that.

Did the legacy app run fine in XP without admin privileges? That would at least rule out the need for admin privileges (though you may still need elevated permissions and/or compatibility mode).

The only other thing is talking to the dev to figure out what dependencies the legacy app has. A pure VB6 app would have worked fine, so obviously there's other dependencies, system files or file locations that app needs to function.

If you don't want to try any of the above, your other option is to just run the program in in VM. Look into running it under XP Mode, or set up a VMWare/VirtualBox VM with Win XP.