jws2bay
asked on
Published Program doesn't run programs, Dreamweaver
I am working with FoxPro 9.0 SP2. I have an application which I have revised and published many times over the past year. Suddenly the application runs fine in the engineering mode, but the published version gets errors "Variable not found". The best I can tell is that the applications fails to call up one of the programs.
I have gone back and built the application making sure that the files are being recompiled, but this has not helped. I have command line compiled the program I suspect of causing the program, but that didn't help.
I'm trying to come up with clues, so this might not be relevant. Just before I ran into this problem I had a problem publishing the application with the InstallShield. When I did the build of a SingleImage I got an error
fatal error - 1501 : Could not compress....
If I close FoxPro and run the InstallShield it will build without the error.
Any suggestions of how to solve this problem would be greatly appreciated.
I have gone back and built the application making sure that the files are being recompiled, but this has not helped. I have command line compiled the program I suspect of causing the program, but that didn't help.
I'm trying to come up with clues, so this might not be relevant. Just before I ran into this problem I had a problem publishing the application with the InstallShield. When I did the build of a SingleImage I got an error
fatal error - 1501 : Could not compress....
If I close FoxPro and run the InstallShield it will build without the error.
Any suggestions of how to solve this problem would be greatly appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Pcelba,
That's the problem. I am doing the build with "Compile all files" and "Display Errors" checked. The application builds without errors.
I expected that the InstallShield problem was a problem that FoxPro was holding on to something.
Olaf,
I had restarted FoxPro, I evan shut down the system, and did a cold start. Still have the problem.
The application compiles without errors. After building the application I tried to run the exe file on the engineering machine. It runs without errors. Install it on another system and I have the error.
The "variable not found" error calls out the variable by name, and it is a variable used in a program being used by a program called from the main application. It is not a field name.
I am in the process of testing the program in other areas to see if I can pickup another clue.
That's the problem. I am doing the build with "Compile all files" and "Display Errors" checked. The application builds without errors.
I expected that the InstallShield problem was a problem that FoxPro was holding on to something.
Olaf,
I had restarted FoxPro, I evan shut down the system, and did a cold start. Still have the problem.
The application compiles without errors. After building the application I tried to run the exe file on the engineering machine. It runs without errors. Install it on another system and I have the error.
The "variable not found" error calls out the variable by name, and it is a variable used in a program being used by a program called from the main application. It is not a field name.
I am in the process of testing the program in other areas to see if I can pickup another clue.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I found the problem.......stupidity
When things just don't add up.....Go back and check the obvious.
Somehow I was building the exe file correctly, but I was releasing a earlier version in the InstallShield.
I thank you for responding to the question. I found my error by adding message boxes to display my variable values in several areas of the program. When they didn't show up, it beacme obvious what I was doing wrong. I'll try to have a real problem next time.
When things just don't add up.....Go back and check the obvious.
Somehow I was building the exe file correctly, but I was releasing a earlier version in the InstallShield.
I thank you for responding to the question. I found my error by adding message boxes to display my variable values in several areas of the program. When they didn't show up, it beacme obvious what I was doing wrong. I'll try to have a real problem next time.
ASKER
I was just doing someting stupid.
InstallShiled can report error when not all files are available for the build. FoxPro can leave some class libraries open (blocked) if the recently finished application did not clean the environment up properly.