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.
We have just migrated to WF 8 recently and are running into different issues with displaying data in our reports particularly Excel 07. We run stored procedures to get our data from our database.
With that said, some of our data contain special characters such as ">", "<", "-", etc. to name a few...some characters are accepted but some are not particularly the "<" and the "-"...these create issue where data in multiple tabs get deleted and/or formatting get messed up where image doesn't show or we'll get a message saying...
"Excel found unreadable content in 'a4h6j{1}.xslx'. Do you want to recover the contents of this workbook?..."
We need these special characters in the report and I have worked around other ones but I'm thinking there's gotta be a way to fix this.
I appreciate any input.
Thanks!This message has been edited. Last edited by: <Kathryn Henning>,
We've been having issues with "special" characters too. We made some significant progress recently by making sure we had the correct code page configured in WF. There are 3 places (that we heard of) where this can be a problem: 1. The WF reporting server (NLS Settings). 2. The WF client (NLS Settings). 3. ReportCaster (RC console then Configuration->Code page).
I suggest you check them and make sure they're set to the same value. In our case (Windoze), the appropriate value is 1252.
WF: 7.7.03, Windows Server 2008, Multiple output formats
You can use 'SET HTMLENCODE=ON' or 'ON TABLE SET HTMLENCODE ON' to eliminate most of the XLSX problems with carats and periods.
Also check your code page can output any special characters in your report. I had XLSX reports bombing out because there were trade mark and copyright characters in several description columns. Using code page 1252 solved this issue.This message has been edited. Last edited by: Michael L Meagher,
WebFOCUS 8.2.03 - Production WebFOCUS 8.2.04 - Sand Box Windows 2012 R2 Server HTML, PDF, Excel In FOCUS since 1980
Posts: 115 | Location: Seattle, WA | Registered: April 07, 2015