I have VB6 running on a windows 7 machine. The program works as intended, however when i go to File > Make [program name] .exe file, the option appears to run correctly, i save the file, then when I attempt to run the program on a server, the associated services do not start.
I have my coworkers create the .exe file and it compiles correctly. None of them are running windows 7.
There is no error message that pops up, I was trying to find some event log that would indicate an issue, and i could not find that either (however I could be missing it, so if anyone can tell me exactly where the log messages regarding the compile are, I'd appreciate it!).
for VB6, i have SP6 installed. I was reading some other posts, and they referenced issues with VB6 and Windows 7 with SP1, which is also installed on my work machine.
If anyone could help me with this, it'd make me really happy. I just got a big promotion to this gig, and if i cant figure this out, its gonna make me look bad.
I'm using VB6 under win7 64 without any issues (yet).
If you have Win7 Pro or greater you could use the virtual xp to host your vb6 install to get you out
of your jam. If you don't have win7 pro or greater, get Win7 pro or greater.
Then you can run xp too and work around your issue.
Is there some add-in that will allow me to do this?
Bitman, do you compile your programs (make the .exe)? Not in Virtual XP mode? Do they start services? i find it hard to believe that i tried it on 3 win7 machines and none would work, but you say you have had no problems? I think were doing different things...
That did work. I was able to make a virtual xp and compile it. Thanks for your help.
The only problem was that the virtual window is tiny as s***, and if i go full screen, it isn't really compatible with my 2nd monitor. I'm sure i could play around with it, but didn't have time today.
There isn't any way to make the win7 vb6 compile correctly without a virtual machine? That is really a load of crap... I understand that Microsoft wants us all to use .net (and for god sakes, its been around long enough) but this is really going to create a butt load of work for me... i would prefer not to have to migrate EVERYTHING over...
And, quite frankly, they shouldn't still be writing stuff in vb6. I am going to bring that up at a meeting im in tomorrow...