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.
Not sure why you would want to chop off the first digit of month since 10, 11, and 12 would not be correct. You can use the following syntax to do that though.
-SET &DTMDDYY=EDIT(&DATEMDYY,'$99999$$99');
Why don't you just use &DATEMDY?This message has been edited. Last edited by: FP Mod Chuck,
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
I used these in define and they are not working. Did you try the code out previously. Essentially the customer want to suppress the leading zero in the month. 05/05/17 to 5/5/17. Does that help?
Is this for display purposes only or will you try to use this variable in your code? If it's for the former (and this is a show stopper) you can use an IF THEN ELSE statement to first find out if your month and day segments are less than 10 and mask out the 0. If it's for the latter, you will not be able to use the manipulated zero suppressed variable for WHERE tests.
You should find out how important this is though, because you're going to create a lot of extra code to satisfy a pretty minor requirement. Someone down the road will need to decipher this code to figure out why you're doing all this stuff. The labor involved in one variable might not be much but once you make it the standard, every report with a date variable will have to look this way and you're now stuck with a lot of extra coding.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
So, if I'm given a spec that says all dates should be treated like this, I'd have to inflate the labor by at least 25% because I know that's not the only place a date will be present in a report or chart. I would also feel obligated to inform the client that this could become an expensive indulgence of a really minor matter of taste and try to talk them out of implementing that specification.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
So, if I'm given a spec that says all dates should be treated like this, I'd have to inflate the labor by at least 25% because I know that's not the only place a date will be present in a report or chart. I would also feel obligated to inform the client that this could become an expensive indulgence of a really minor matter of taste and try to talk them out of implementing that specification.
Totally agree with Babak. That request doesn't worth the effort and the maintenance that it will need in the future...
Furthermore, manipulating the date as specified may result that all date function won't work anymore without putting back the leading zeros. Can you image all the work that this change will cause ?...
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013