CSV data export not as expected like xls

English Forum
1

Hello,
I have created a layout specific for export in CSV and/or XLS format.
The idea was to have each line with the corresponding information of the columns (raw dataset).
The xls file shows properly each data column on the respective cell.
Issue on CSV is that (perhaps due to the column width) the data inside is longer than the available width defined on the layout and breaks the line. This leads to a new line only to show the remaing data under that column and all others are blank, just to be alike the preview.
I found this post Text zeilenweise trennen - #2 by Johann_Wagner that looks to me saying this is not supposed to happen cause there is no support for line break in the column, but looks that it is what is happening in my case :stuck_out_tongue:
preview_99_21_144_1_1_1_date.zip (287.6 KB)

Can please someone help me in making the CSV work as intended?
Thanks

2

Hi Carlos,

it seems that the export target “Text (Layout) Format” is used to export to TXT/CSV? In this case, an attempt is made to implement - as far as possible - the designed layout, which then leads to a line break because the content is simply too long. But in your case you don’t want the line break, so please you the export target “Text (CSV) Format” instead. There the layout is not preserved in any way, this is purely a data conversion export.

image
image706×439 20.5 KB

Various export options are available via the “Options” button (separator, framing, how to deal with header and footer lines) to customize the export accordingly.

image
image706×406 23.2 KB

These options can also be specified in the application code.

The result should then look as it is expected.

Best regards
Chris

3

Hello @crauchfuss ,

Thanks for reply.
Unfortunatelly, that was the option selected, and i´ve tried with all export settings available to see if any would produce the desired output - none did.

ExportSettings
ExportSettings1360×776 22.1 KB

Could it be something from the layout itself?
I have attached the .lst file on original post so anyone can check if i made any mistake on any property…

Any other ideia?

Thanks

4

Hi @Carlos

the screenshots don’t fit to the expected and actually exported files. There is no separator (, according to the screenshot) and no framing (" according to the screenshot) in the actual export file.

Not from the layout itself, but from the source code of the application.

For testing purposes we took your LST file and minimized it as far as possible and used a sample application passing the two records (we’ve used your PDF export as a guide). The results are shown in the screenshots below. The export options that are actually used can be seen in the Debwin log file, e.g.:

Debwin4::CSV::V1;TypeCode;Timestamp;Level;Logger;Thread;Properties;Message
▪;1000;08.10.2024 14:34:49.551;1;LL.Generic;4A78;100:2=CMLL27♦101:1=4;     [cmll27EX] TXT.SeparatorChar='BLANK'
▪;1000;08.10.2024 14:34:49.552;1;LL.Generic;4A78;100:2=CMLL27♦101:1=4;     [cmll27EX] TXT.FrameChar='NONE'

A Debwin log file could provide further information or insights.

image
image1265×732 36.9 KB

image
image1265×715 37.7 KB

5

Good morning @crauchfuss

I had another idea: what about previous versions?
So i took a .lst created with LL15 and then used several newest DLL versions to run it and check the output.
I came up to version25 and that is OK(the data is shown raw with a separator), but since DLL26 the layout start to be has i raised in this issue.
Has you suggested i´ve used debwin to see the logs and can confirm that the LlPrintGetPrinterInfo is the rigth option (CSV format) selected but results vary depending of the DLL.
I attach the logs from both versions along with the output created with each and also the .lst file.
So is there a need to do some change on the application code that i am not aware? If so, could you kindly provide me the link with that specific details, please?

Thanks
csvLog4DLL.zip (2.8 MB)

6

Hi @Carlos_Carvalho,

I apologize for the late response.

The logs are different from the results, that’s true. The LL26 log and export result are different. Was the export performed directly or from a preview (LLViewer or PreviewControl?). To be honest, both versions are outdated and are no longer supported. Do you have a way of testing the export with a more recent version LL28 or LL29? We would like to make sure that we are not chasing a problem that we have already fixed in a more recent version.

We have tested it down to LL27 SP2 but have not been able to reproduce it.

Chris

7

No problem @crauchfuss

I attach the log and csv of version LL29 for your analisys.
Is not printed has i want (comma separated values), but instead has spaces to have the same format like a preview :frowning:
The export was performed directly.
By any reason up until LL25 the export is has i desire, but since then (inclunding 29 with this test) the csv export is not working accordingly.

What do you mean when saying ‘not been able to reproduce it’ ?

Thanks and Regards
Carlos

LL29csvExport.zip (1.0 MB)

8

It means that we have tried to provoke the behavior. We used our sample application and also various test applications that we programmed ourselves. But we were not able to reproduce the behavior.

Thanks for the log. The problem seems to be that part:

Debwin4::CSV::V1;TypeCode;Timestamp;Level;Logger;Thread;Properties;Message
:black_small_square:;1000;15.10.2024 11:24:18.694;1;LL.Generic;FE9C;100:2=CMLL29​:diamonds:101:1=3; [cmll29ex] ERROR! m_nProjectType=0, no table only export possible

For some reason the project type is not transferred (ProjectType=0), this should actually happen automatically when the project is loaded. We would need this in a minimized sample to see what is going wrong, so I think it s a case for our support team, we would like to have the app or a sample.

1 Like