Kbase P142442: Why isn't the startup parameter I specified in Architect taking effect when I run my code?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/6/2009 |
|
Status: Unverified
GOAL:
Why isn't the startup parameter I specified in Architect taking effect when I run my code?
GOAL:
In what order does Architect use the different places where startup parameters can be specified when running code?
FACT(s) (Environment):
OpenEdge 10.2x
Windows
FIX:
Architect build the list of startup parameters differently depending on whether you are running your code using the default run configuration or whether you have created your own run configuration.
When running using the default run configuration the list of startup parameters are built as follows:
- We grab the system wide parameters (Window->Preferences->OpenEdge Architect->Startup)
- We then append the parameters from the Project (Properties->OpenEdge)
When running using your own run configuration the list of startup parameters are built as follows:
- We first grab the list of parameters as shown above and build a static list of parameters that goes on the command line
- That command line is then static from that point on. We do not go back and merge any changes you make to the global or project parameter settings back into the run configuration.
- You then make whatever changes you want to the command line parameters
For a run configuration the only things that are dynamic are the places where we give you a check box with the "Use Project <whatever> settings" option.