Can a .exe created using Application compiler toolbox read input data from an Excel file each time it is executed?

I have created a .exe file using the Application compiler toolbox and it reads the input data from an Excel file. The problem is that it reads the input data during the creation of the .exe file it saves this data forever, when I edit and change the input data the .exe remains calculating with the old input data. I need to know if there is a way to achieve this.

Thanks,

Jon

[Rik]

Do you have code that will read from the file when starting your function? Or did you put that file as required file when compiling?

[Mario Malic]

"when I edit and change the input data the .exe remains calculating with the old input data. I need to know if there is a way to achieve this. "

I guess you need to create a button that you will click to re-read the Excel file again.

[Jon Millan]

I have code that will read from the file, but when I build the .exe file, the Excel file appears as required file and I cannot delete it.

I will try it by creating a button to read the file using GUIDE, I supose that GUIDE is the best way to interact with buttons, isn´t it? I will try it and I will tell you how it works.

Thanks.

[Rik]

GUIDE is not 'the best way' to create a GUI in Matlab. It is 'a way' at best, and it will be removed from a future release. For general advice and examples for how to create a GUI (and avoid using GUIDE), have look at this thread.

[Jon Millan]

It has worked using a push button, thanks.

Answer 1

[Walter Roberson]

If you read from a fixed filename in your code, then MATLAB will take a copy of the file and will build it into the executable. It will be unarchived into a temporary directory when the executable archive is expanded, and can be read from and written to inside the temporary directory. If the temporary directory is deleted, then any updates to the file are lost, and the next time the archive is expanded the file will be back to what it was. See the documentation for ctfroot()

If you want to be able to update a file and have it "stick" then the updated file needs to live somewhere else. For example you can check the USERDRIVE and USERPATH environment variables to construct a path relative to the user home directory, and if the file is there then read it from there and otherwise read the one that got copied into the executable.

[Jon Millan]

Interesting, now I know why it does not work as I want. I will take a look and learn how USERDRIVE and USERPATH work.

Thanks