• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 558
  • Last Modified:

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.


0
jws2bay
Asked:
jws2bay
  • 3
  • 2
2 Solutions
 
pcelbaCommented:
Compile and build the application with debug info and record the exact line number where the error occurs. It should also tell what variable is missing and this info should be sufficient to fix the bug in code or identify missing part.

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.
0
 
Olaf DoschkeSoftware DeveloperCommented:
I often restart foxpro before doing a build. And of course close foxpro before copying the project to backup or using it as a source for Installshield.

I second the recommendation to compile with debug info and log error data including lineno() but even better the whole arrays AERROR() and ASTACKINFO() create and memory variables via SAVE TO MEMO memoVariables ALL, which storeas all global and local variables into a memo field you should have in the error log table. You can restore via RESTORE FROM MEMO memoVariables ADDITTIVE. (ADDITIVE being optional) to see what the situation was, when the error occurred.

Also, what I remember now is, that "variable not found" can be a misleading error. As you can adress both variables and fields in source code in the same general syntax - their name - vfp might judge it's missing a variable, while it's missing a field due to a table structure change.

Bye, Olaf.
0
 
jws2bayAuthor Commented:
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.

0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
pcelbaCommented:
This kind of errors is easy to trace obviously. The variable maight be released accidentaly, it may be hidden etc. You should also make sure if it was created or not (place a message window after its creation).

Do you have some error log produced when the error appears?
0
 
jws2bayAuthor Commented:
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.



 
0
 
jws2bayAuthor Commented:
I was just doing someting stupid.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now