RELATED: How to Change Windows' Default Currency from Dollars to Euros The new separators are automatically inserted into all the numbers in your workbook that use them. For our example, we are using a comma as the Decimal separator and a period as the Thousands separator. Enter the character you want to use for each in the edit boxes and click “OK”. The “Decimal separator” and “Thousands separator” edit boxes become available. In the Editing options section, click on the “Use system separators” check box so there is NO check mark in the box. Click “Advanced” in the list of items on the left. I tried putting in correctly formatted dummy data into the Excel-File and set it to Overwrite - not working.The Excel Options dialog box displays.
I tried pre-formatting the Excel-Destination file's columns to my desired format - not working.
The Excel Connection Manager's LocalID setting is set to German, so it should produce correctly formatted numbers. The problem is that Visual studio is previewing the SQL input in the correct formats, the numbers do have a decimal comma, the input is 100% correct - but at some point the comma is being transformed into a period without my doing. I've tried every form of data conversion, doesn't matter if it's DT_NUMERIC, DT_DECIMAL, DT_CY, it's always giving me a decimal dot - even when going the Derived Column route, specifically turning the values into DT_WSTR, then replacing every "." with a "," and then converting to any numerical format still gives me a result with decimal points.
1234.56) - that's not how I want it, I can't work with that. 1234,56) - that is how I want it, that is how it's always worked, that is how I want the final data to be formatted in Excel.įor some reason Visual Studio / SSIS is always transforming this data to a decimal point format (e.g. The data that comes from the server comes with a decimal comma (e.g. I'm trying to create a very basic package that copies data from my SQL server into an Excel file.
0 kommentar(er)
