new version of .exe not executing

[ivant34]

Just got a new laptop, lenova T61. I used to have ibm T41.
The old version of the .exe that I created in T41 can run in the T61.
I just created a newer version of an .exe in T61. When I install the new version into someone's T61 laptop, the .exe does not execute but it does execute in my T61 Laptop

I created the .exe with Visual Studio 6 and VB6.
Absolutely nothing happens, when I execute the .exe all I get is a "DING" sound

No errors are being raised at all. I checked task manager, the .exe doesn't even appear in the process list.

I created an install package and I also just created the .exe. Either method gave the same results.

I also checked the referenced .dlls

What is happening here?

 

[Glasgow]

Is it not likely that the EXE is actually executing but hitting a condition that is causing it to exit immeiately (e.g. missing file or registry setting)? This could be happening so quickly that there is not time to see it in Task Manager.

Why not start by coding in a single MsgBox as soon as practically possible in the code then rebuild the EXE. Assuming the MsgBox executes within the new EXE, this is at least evidence that the EXE is running (and should show in Task Manager).

I would then suggest inserting a series of MsgBox calls in strategic places in the code to determine just how far it's getting when running as an EXE. Eventually you should be abl to tie down the condition that's causing it to exit.

 

[ivant34]

I did code a MsgBox as soon as the app loads. The MsgBox didn't appear at all.

 

[dilettante]

Are you sure it isn't the "Critical stop" sound?

This can be caused by various load errors. In VB6 programs it is most common when a program tries to call InitCommonControls() too late, i.e. after the common controls library has already been loaded.

If you are using this to force loading of Common Controls 6.0 via an application manifest you should make the call before any Form is loaded. Trying to do it during Form_Load or other Form events will be too late except under narrow circumstances. Such a program may seem to work one day and then fail the next, usually after a seemingly small program change.

 

[TysonLPrice]

Just to rule out some of the items mentioned create a new form with just a message box on it, point to it as the start up form, and see if it displays.