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.
I'm converting some old reports to XLSX format from EXL2K format. I have a field that is an age group field. Two of the values in the field of <2 and >=13. EXL2K handles these just fine. When I run the report with XLSX format, the report dies when Excel 2010 opens the sheet saying there is unreadable data. To be clear, WebFOCUS generates the report just fine, it is just when Excel tries to open the sheet that I get the error. I tracked it down to these values. I'm guessing the Excel 2010 is taking the strings <2 and >=13 as the start of a formula. To get around this I have to put an extra quote mark as follows:
original line
EVERAGE/A4=DECODE ADOPT_AGE(1 '>2' 2 '2-5' 3 '6-12' 4 '>=13' ELSE ' ');
new code
EVERAGE/A5=DECODE ADOPT_AGE(1 '''>2' 2 '2-5' 3 '6-12' 4 '''>=13' ELSE ' ');
Just curious if anyone else has come across this?This message has been edited. Last edited by: jgelona,
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
Does it still die if you add ON TABLE SET HTMLENCODE ON to the TABLE-request?
Strictly speaking, that setting should probably be named XMLENCODE instead (and implied when using format XLSX), but the effect is the same.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :