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.
What I have is a -INCLUDE that sets the default start date to the previous 28 days. This works for my HTML pages but the focexecs that the users create themselves who do not use HTML pages, I don't want them to have to enter the dates every time if they don't need to change those values.
Windows, All Outputs
Posts: 55 | Location: Phoenix | Registered: March 01, 2018
Bear in mind the order of execution: Autoprompt is triggered by a static analysis (pre-scan) of the code, before any lines (whether DM of FOCUS) in the fex are executed. At that point, none of the amper vars have actually been instantiated. In shore, Autoprompt can only assemble prompting text based on the static content of the fex file.
To overcome that you'd have to generate fex code dynamically, in which the computed values are hardcoded in the -DEFAULT statements, and then (after a -RUN) EX or -INCLUDE it (in a manner that gets by the client-side pre-scan). But I'd hestiate to venture out on that limb in a production application.This message has been edited. Last edited by: j.gross,
- Jack Gross WF through 8.1.05
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005