Kbase 13937: User's application exits to Procedure Editor: how to fix
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
User's application exits to Procedure Editor: how to fix
Also see Knowledgebase entry 15724, How To Terminate a Smart
Application back to the OS, to see how to do this with SmartObjects.
When an application exits and brings a user to the PROGRESS Procedure
Editor instead of the operating system, this is due to one of two
possible causes:
(1) The application was run from the Procedure Editor.
(2) The application was run directly at startup (i.e., with the -p
startup parameter) but did not end with a QUIT statement.
The reason for (1) is that we assume that when a program is run from
the Procedure Editor, the programmer will want to return to the
Editor upon leaving the program. In other words, this is
a "unit testing" condition. (Considering the alternative makes the
reason more clear: if we were to force programmers to restart
PROGRESS completely each time they test-ran a procedure it would
cause a great deal of inconvenience.)
The reason for (2) is that a QUIT statement should be used whenever
a programmer wishes to return to the operating system prompt (or to
the native windowing environment) upon completion of the application.
If no QUIT statement is present, PROGRESS will return to the
Procedure Editor.
If a user has started a program using the -p startup parameter
and not by running from the Procedure Editor, the QUIT statement
should be used at the end of the program to assure a complete exit
from PROGRESS.
If the program specified with the -p startup parameter is a complex
one with many possible exit conditions, you can just create an
intermediate program that runs the program in question, and then
quits:
mpro <mydb> -p dummy.p
/* dummy.p */
run <the-real.p>.
quit.
Progress Software Technical Support Note # 13937