Visual Basic, VB6 program becomes a DOS program when compiling

VB6 program becomes a DOS program when compiling

Author	Message
Erik Holmquis #1 / 5	VB6 program becomes a DOS program when compiling I have compiled my VB6 application hundreds of times using "Make excutable...". But suddenly the EXE file is not a Windows program - it is a DOS program! When running the EXE file a DOS window is opened and then immediately closed. I don't get any compile errors, and the size of the EXE file is the same as before. What has happened? / Erik Holmquist
Tue, 31 Aug 2004 17:29:01 GMT

st.. #2 / 5	VB6 program becomes a DOS program when compiling Quote: > I have compiled my VB6 application hundreds of times using "Make > excutable...". But suddenly the EXE file is not a Windows program - it is a > DOS program! When running the EXE file a DOS window is opened and then > immediately closed. I don't get any compile errors, and the size of the EXE > file is the same as before. What has happened? > / Erik Holmquist It's not likely it has become DOS program. Besure to check your code to makesure your not creating a console window or launching a DOS program or .bat file. If you are then there may be no way to avoid it the console window from poping up. -steev -- Stephen Fonnesbeck Remove NOSPAM. to email.
Wed, 01 Sep 2004 10:08:53 GMT

Erik Holmquis #3 / 5	VB6 program becomes a DOS program when compiling OK. Maybe it's not a DOS program. But the properties are like a DOS program and the EXE icon is like a DOS program. The problem appears on my client's workstation, not on mine. The folder that contain all modules that are included in the EXE file is now identical at the two workstations. We will now try to reinstall VB. / Erik Quote: > > I have compiled my VB6 application hundreds of times using "Make > > excutable...". But suddenly the EXE file is not a Windows program - it is a > > DOS program! When running the EXE file a DOS window is opened and then > > immediately closed. I don't get any compile errors, and the size of the EXE > > file is the same as before. What has happened? > > / Erik Holmquist > It's not likely it has become DOS program. > Besure to check your code to makesure your not creating a console window > or launching a DOS program or .bat file. > If you are then there may be no way to avoid it the console window from > poping up. > -steev > -- > Stephen Fonnesbeck > Remove NOSPAM. to email.
Fri, 03 Sep 2004 17:57:33 GMT

st.. #4 / 5	VB6 program becomes a DOS program when compiling Ah, reinstalling would be my recomendation as well. When distributing VB apps you need to makesure the client machine has all of the dependant files in order for the app to run correctly or at all. Reinstalling VB will mostlikly restore any missing or corrupt VB files if, in fact, that is what's causing it to fail. make sure you get the latest service pack on it as well. -steev Quote: > OK. Maybe it's not a DOS program. But the properties are like a DOS program > and the EXE icon is like a DOS program. The problem appears on my client's > workstation, not on mine. The folder that contain all modules that are > included in the EXE file is now identical at the two workstations. > We will now try to reinstall VB. > / Erik -- Stephen Fonnesbeck Remove NOSPAM. to email.
Sat, 04 Sep 2004 10:27:00 GMT

Erik Holmquis #5 / 5	VB6 program becomes a DOS program when compiling The problem is caused by Trend OfficeScan Anti-Virus software. We have been using this program for a while, but the problem didn't appear until last week. So some engine or virus definition upgrade must have caused it. If we stop the OfficeScan services it works. / Erik Quote: > Ah, reinstalling would be my recomendation as well. When distributing VB > apps you need to makesure the client machine has all of the dependant > files in order for the app to run correctly or at all. Reinstalling VB > will mostlikly restore any missing or corrupt VB files if, in fact, that > is what's causing it to fail. make sure you get the latest service pack > on it as well. > -steev > > OK. Maybe it's not a DOS program. But the properties are like a DOS program > > and the EXE icon is like a DOS program. The problem appears on my client's > > workstation, not on mine. The folder that contain all modules that are > > included in the EXE file is now identical at the two workstations. > > We will now try to reinstall VB. > > / Erik > -- > Stephen Fonnesbeck > Remove NOSPAM. to email.
Sat, 04 Sep 2004 16:47:51 GMT

Page 1 of 1

[ 5 post ]