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.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
That is interesting to know. I am familiar with the FTOA function. I ended up creating a DEFINE FUNCTION due to the fact that my calculation has a number of steps. The return value from the function is an A16 so the DM varialbe handles the value fine. In the FUNCTION I use the PTOA function to convert the final numeric value to Alpha.
This might not mean anything to you but hears the code I created.
This DEFINE FUNCTION capability in WF is great when you need to massage a data value supplied by a user. For example, our users enter a date range to select records. The problem is that the date/time values in the database are stored as the number of seconds from January 1, 1970 and are based on GMT instead of EST or DST time. Therefore I need to do a bunch of calculations to translate the dates entered by the user into values I can then plug into the WHERE clause. Doing this with a DM variable allows me to plug the raw values directly into the WHERE clause. This makes it possible for WF to build the SQL to pass to the database. If I called the DEFINE FUNCTION from a DEFINE field or from within the WHERE clause, the WHERE clause would not translate to SQL, forcing WF to pull all the records back and then process the selection, etc. etc.
Thanks!
Mickey
FOCUS/WebFOCUS 1990 - 2011
Posts: 995 | Location: Gaithersburg, MD, USA | Registered: May 07, 2003
Mickey, Remember that all numeric calculations in DM are integer. That is the reason for the ***. Also, you can input numbers with a decimal point and digits after the decimal point but in any calculations the results will be integer. When using FTOA, the result is alpha hence no problems.
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
Posts: 1980 | Location: Tel Aviv, Israel | Registered: March 23, 2006