Issues, VB 6.0 Apps on Vista and Windows 7

mlcktmguy
mlcktmguy used Ask the Experts™
on
User are requesting to run the VB 6.0  app we developed several years ago on Vista and Windows 7.  I am wondering what, if any suggestions other VB 6.0 developers may have concerned with installing and running VB 6.0 apps on these platforms.  surely we are not the first.

We are using the latest version of InstallShield 2010 Professional to create our install.

We have encountered a very specifc isssue related to a 'Kill' command that is not deleting a file, yet not throwing an error.   I detailed in that scenario in topic
http://www.experts-exchange.com/Programming/Languages/Visual_Basic/Q_25085694.html.  This issue had not been resoved yet.

I am just trying to anticipate other issues that we may need to address runniing on these newer platforms.  Any applicable suggestions will be greatly appreciated and points will be split among them.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2009
Commented:
I have many VB6 apps, and they run fine on Vista (they are still compiled on XP, just FYI). The Kill command works too (or either no one has executed that particular routine and found the error, which I highly doubt). I do know the SendKeys comand no longer works, although you can find solutions to that problem here on EE. I don't use that command, so it hasn't affected me.
I have users that have installed my VB6 apps on Vista without hearing a peep from them. Others (who probably installed without Admin rights) I've had to tell them to modify their desktop shortcut to run the program in Windows XP compatibility mode, and also to "Run as Administrator". One guy I had to have him go back to our CD and right-click the main setup and select "Run as Administrator" so the DLL's and OCX's would get registered. See, I have a main Setup.exe that installs all the DLL's and OCX's, then each program in my suite (26 of them) have their own separate installation tha just installs the program itself. I use legacy pre-Symantec Wise Pro V9 for my installations.
As for Win7, I need to do further testing, as it doesn't like an in-house written DLL. I am getting a Win7 box to make sure the Admin rights thing wasn't the problem. If it is a problem, I'm hoping running Virtual Machine on Win7 and going into XP Mode will allow my programs to run on Win7. I've read good reports about this scenario here on EE and have high expectations for it if I need to go that way. However, the enduse has to have Win7 Pro, Ultimate, or Enterprise version to run Virtual machine/XP. Home or Premium won't cut it.
Well, that's what I know so far, I hope it is of some help.

Author

Commented:
Thanks for your input.  We had been warned about the requirement for Administrator rights and used an admin user to install.

Just out of curiosity where do you install the app and data for the VB6.0 apps you are running in Vista?  

After doing some more research it looks like Vista and Windows 7 handle the \Program Files directory differently than XP.  We have booth the application and the related data being installed in \Program Files.  Perhaps this could be an issue.
Top Expert 2009
Commented:
Funny you mentioned that. I NEVER install anything in "Program Files". I always install directly under the root of the C drive. For instance, "C:\MyProgram\MyPrg.exe". I am probably one of VERY few people who do this, but I do so for a couple of reasons:
1. When I first joined the company, the programs (two at the time) were DOS-based and ran on DOS machines.
2. When Windows came along, I just kept the "under the root" convention to avoid confusion among my users, and so I'd know when troubleshooting over the phone, where their app was located.
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Top Expert 2009
Commented:
Oh, and by the way, keeping my programs under the root of the C drive avoided the error I'd get with some old code where a space in a path wasn't allowed or expected (like the space contained in "Program Files".
Commented:
I am not sure about Kill statement; as I have not used this in my recent projects, but I am using VB6 application under Windows 7 without any problem; except I am getting error on SendKey while running the appliation from IDE; other wise with Compiled EXE SendKey is also working without any flaw.

I am usind ODBC Data source (for Access MDB) in some of my older applications; so I have to Initially run the exe "As Administrator"; I Install the software in Program Files Folder; but keep the Data File (MDB) in diffrent folder.

I am also using Crystal Reports (8.5) integrated with VB6; Initially I was getting problem opening DSR files; but since I ran VB6 EXE in Windows XP compatibility mode; that problem has gone.

I am using classic Visual Studio Installer to install my applications.

Vinod
Commented:
I tried putting data (MDB) in Program Files folder; then also ran the software without any problem; I figured Windows 7 protects direct editing or saving of files in Program Files Folder; as I tried to save INI file located under sub folder of Program Files; System did not allowed me save the file at original location; I had to save the file in other folder and then copied the same Program Files Folder; (So I suspect system will also not allow Kill file in Program Files Folder).

This is very annoying for me; at the same time feel good; as my users will keep away from changing these settings out of curosity and I will get less phone calls for their wrong doings with INI file.

Vinod

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial