How do you know if a call to "writetable" is successful?

Hello,

I'm sure that this is elementary, but what indicates that a function call that doesn't have an output proceeded properly? Like that "writetable()" actually did write as designed? The old "xlswrite" had a status output. Why doesn't writetable have that?

I guess the same question would be valid for "print".

Thanks!

Doug Anderson

[Douglas Anderson]

And also for "save"!

Answer 1

[Walter Roberson]

An error condition would be generated if writetable() or save() fail.

Exceptions:

• if the operating system or file system messes up and accidentally writes incorrectly data then you might not get an error message: they might believe that it worked when instead it created a mess
• if the file is being written to a network file system then it is not completely certain that an error will always be reported.

[Douglas Anderson]

Thank you, Walter. In the past, to give a response if xlswrite() failed in deployed code, I would write my own error message (based upon output "status") that would alert the client that there was a problem. Now with writetable(), the error now would just give the error "ding" that doesn't give a clue as to what went wrong. If I get an error running the code myself, I see the error in the Command Window. The client just hears something bad.

Am I missing something? Again, thank you.

Doug Anderson

[Walter Roberson]

Use try/catch

[Douglas Anderson]

Once again, Walter, thank you!