However - when export to Excel - it blows up with the the following message
Removed Part: /xl/sharedStrings.xml part with XML error. (Strings) Illegal xml character. Line 75, column 26. Removed Records: Cell information from /xl/worksheets/sheet1.xml part
I was able to track this down to a specific row - and specific field in the report....the address.
Community Center, 1425 – 4th ST NE, Somewhere, MN, 55123
Converting to Hex - I can clearly see the issue is the "dash".
The dash is secretly a hex value of 1f
When I manually remove the dash - or convert said dash to a 2d hex value - it works fine.
What's the best way to address this? I'm pulling from a Unicode SQL server table. I'd prefer, if possible, to avoid doing a string replace/CTRAN - because I think if the 1f/Unit Separator field is giving me grief now - I'm guessing there's some other data that will too.
Same goes for the report - if I can turn it on in this report - I'm sure it'll blow up in some other report that pulls in the address field.
Is there some other server setting that allows the 1f field to export to XLSX?
I read about the NLS - but I'm not sure if that's the right solution. Could be - but I'm more of a code geek than a configuration geek - so I may be interpreting that incorrectly. Our CODE_PAGE is set to 437 - U.S. English and the LANG is set to AMENGLISH.
Any suggestions?This message has been edited. Last edited by: <Kathryn Henning>,