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 several focexecs that have the Define "SP/A1 = HEXBYT(160, 'A1');" which is used to display a space on reports. After going to R7.7.02 it now displays as a lowercase "a" with a tic mark above it (á). Hopefully this is just a setting that needs to be changed.
Has anyone seen this before?
Thanks, TedThis message has been edited. Last edited by: Kerry,
Dev Studio 8.0.09 App Studio 8.2.01 DB2, FOCUS PDF, HTML, Excel, CSV In Focus since 1983
what was the fix to this? I'm having this problem as we go to Linux from Windows. Funky characters are appearing on webfocus reports instead of a space and looking at the data #160 is at the end of the field ... This issue is showing as closed, but not sure what the fix is that closed the issue.
Originally posted by ABT: @Prarie - a subtle difference is that 160 prints a physical space character whereas 32 prints the html space entity ( ).
It is the other way around actually, 32 is a physical space and 160 is a non-breakable space. HTML folds multiple consecutive spaces into a single space, but doesn't do that with non-breakable spaces.
I notice that in the standard Windows encoding (CP 1252 or something) ALT-160 results in an á, which is what the OP is seeing.
If you're outputting HTML (where a non-breakable space makes sense), you can get the same result by using or   instead of using HEXBYT().
Alternatively, figure out which encoding is being used in HEXBYT() (the encoding of your reporting server) and try to find the appropriate decimal code for the non-breakable space in that encoding. Or change the encoding of your reporting server to match your desired output encoding, but that probably has interesting side-effects.
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 :