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. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at firstname.lastname@example.org and provide your corporate email address, company, and name.
You should use SET &ECHO='ALL'; and with -EXIT command find out which lines of code is causing this issue. In the final display PRINT/SUM, try using PRINT * END - to check if the issue is in final table file command.
I had a problem with some special characters in Excel but I was getting blown up in the Excel not webFocus but here is the results of that case. the solution worked so good luck woth checking these settings though.
Thank you for providing the requested files and information. It's great that the suggestion from Focal Point resolved your issue. There are two options possible in this case: 1. You can either stay with the solution offered in the forum, that is using character encoding 137. 2. Or you can use a different character encoding - Windows-1252 - which is a new standard for HTML 5, and should also work in your case. The Windows-1252 char encoding is a superset of ISO 8859-1, and I am including a link to the description of this encoding below: http://en.wikipedia.org/wiki/Windows-1252 For this option you will need to set Reporting Server Admin Console in Workspace -> NLS to CODE_PAGE "1252 - Windows (Latin 1)" Client Admin Console -> Configuration -> NLS Settings to 1252 - Western European Tomcat Configuration for Java Options to -Dfile.encoding=ISO8859_1
WebFOCUS 8.0.7 DS 8.0.7 AS 8.0.7 Windows Output: Excel, HTML, PDF, AHTML,Mobile In Focus 1982
There are various cases because of which this error appears. Better to try the report first in HTML. If that works then it might be huge data or special characters. In next step try to limit the records eg. 1000, 5000, 50000 etc. If that works then check for special characters. Sorry but no sure shot root cause and solution. It can be done step by step only. SET &ECHO='ALL'; and with -EXIT Given by Ram Prasad is a very good option to debug.
Thanks, Pravin Singh
WebFOCUS 7703 Windows, All Outputs pravinsinghwebfocus.blogspot.com
Just FYI - our classes haven't used the CAR file in many, many years. Our need for more robust technical training examples exceeded the awesome simpleness of the CAR file long ago. Most of our classes now use a pretty robust SQL Server data mart which allows us to address many relational situations. And since a huge percentage of our user base access relational tables of some kind, this is a better approach. However, the CAR file lives on in every installation, so it can still be used for reproductions, and old car price jokes! Ha!