VB app runs only on the PC it is compiled on.

[William Henderson]

I am a consultant who inherited a VB6 program utilizing SQL 7.0 for the backend.
The pogram will compile and run. But the moment you try to install it on
another machine, it will not run on that machine. All we here are two quick
beeps. The program does not even get to the first line of code, it dies while
windows is trying to load it.
We moved the cource code to another PC, compiled it and it ran fine. We moved
the executable back to my PC and it will not run. All we hear are the two
quick beeps.
The program is using the data environment variable (which I believe to be
the culprit).
Dev environment is NT4 w/ SP5
Target environment is NT4 w SP5, Win98

Have you ever encountered this before? Any suggestions?

[Dan Appleman]

Sounds like a typical DLL **** dependency problem. Missing DLL, misregistered
component, obsolete version - anything that might raise a runtime error that would
cause the program to fail.

You might check out our VersionStamper program (www.desaware.com) - it's good for
resolving and preventing that type of problem.

It could also be any number of other configuration problems, but DLL **** would be
my first guess.

Best of luck - these things can be tricky.

Dan


William Henderson wrote:

> I am a consultant who inherited a VB6 program utilizing SQL 7.0 for the backend.
> The pogram will compile and run. But the moment you try to install it on
> another machine, it will not run on that machine. All we here are two quick
> beeps. The program does not even get to the first line of code, it dies while
> windows is trying to load it.
> We moved the cource code to another PC, compiled it and it ran fine. We moved
> the executable back to my PC and it will not run. All we hear are the two
> quick beeps.
> The program is using the data environment variable (which I believe to be
> the culprit).
> Dev environment is NT4 w/ SP5
> Target environment is NT4 w SP5, Win98
>
> Have you ever encountered this before? Any suggestions?