Reading CSV file within Matlab exe gives unexpected result

Hello,

I have a Matlab script that I want to compile into a standalone exe. The script reads a CSV file (the path to which is input from the user). It uses readtable with options coming from detectImportOptions. Everything is OK in the script, but when compiled, the CSV file is not read properly. I could track that and saw that the import options are very different compared to those that I get when I execute the script within Matlab.

Is this a well-known issue? Any proposals to go around it?

[Jeremy Hughes]

Hi @Yazan

Without a file or code to look at, it's really hard to say anything at all about what you should expect.

Remember that detectImportOptions generates options based on the input file being passed in. If the files are not the same, you may not see the same options being generated. Even subtle differences in files can result in different options, especially for smaller files.

Some differences might also result depending on the locale settings where the code is executed if the data contains dates.

[Yazan]

Hi @Jeremy Hughes

Thanks for the reply, and sorry for coming back late to this question. My problem was solved by decrypting the CSV files before being used by the Matlab exe (the files were encrypted).

Answer 1

[Yazan]

Problem was solved by decrypting the CSV files before being used by the Matlab exe (the files were encrypted).