Activity overview
Latest activity by ndmobil
FYI, this seems to be related to the regional settings in windows -- more precisely the decimal separator and grouping symbol. Setting them to the US standard of . for decimal and , for digit grouping (for me in germany it would be the other way round) "fixes" the problem. [image] [image] [image] / comments
FYI,this seems to be related to the regional settings in windows -- more precisely the decimal separator and grouping symbol.Setting them to the US standard of . for decimal and , for digit groupin...
SBuckVRT said:
Hello - I am still experiencing this issue on SQL Prompt version 10.13.31417. SSMS version 18.12.1. Fields are all varchar. <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Created with Liquid Studio 2021 (https://www.liquid-technologies.com) -->
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
<logFileName>error061400_01.xml</logFileName>
<summary>Errors were detected in file 'C:\Users\SBUCK\AppData\Local\Temp\qajqgaai.rrl\Exported results 2022-11-29_11-45-46.xlsx'</summary>
<repairedParts>
<repairedPart>Repaired Part: /xl/worksheets/sheet1.xml part with XML error. Catastrophic failure Line 1, column 0.</repairedPart>
</repairedParts>
</recoveryLog>
Same here --- exporting to excel when the results include numerics/decimals yields the quoted error. / comments
SBuckVRT said:
Hello - I am still experiencing this issue on SQL Prompt version 10.13.31417. SSMS version 18.12.1. Fields are all varchar. <?xml version="1.0" encoding="UTF-8" standalone...