As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
I believe our user wants to use the same procedure as Adhoc versus scheduled job Via ReportCaster. When its scheduled we need it to run with defaults and when we launch it adhoc, we expect to pass some parms. Thanks in advance.This message has been edited. Last edited by: vaayu,
Posts: 289 | Location: Houston,TX | Registered: June 11, 2004
BabakNYC, The requirement is to enable/disable prompt based on a flag so thats why I have a DEFAULT in one place and DEFAULTH in another place. We want to control the prompting based on a flag. Hope it makes sense
Your problem is with autoprompt. It isn't smart enough to follow conditional expressions.
In this case, it sees the -DEFAULT before it sees the -DEFAULTH, so it prompts for a value.
That suggests that you could invert your condition, putting the -DEFAULTH inside it and skipping to the -DEFAULT otherwises, but that won't work either; autoprompt will then see -DEFAULTH before -DEFAULT and never prompt.
What would work is to put both conditional sides into a separate file each and include the remainder of your procedure after that. Then, in the case that the user runs the truth-side procedure, she gets a prompt, and if she runs the falsehood-side procedure, she won't.