>>If it is true that the regular Save feature of the new Excel produces an incompatible file format, and if an existing vfp-application uses IMPORT to import such an xls-sheet, then that existing app will gonna crash, right?
>>
>Hi Peter,
>
>Any command may fail due to many different reasons. I assume the application has error handling in place and therefore won't crash, but will gracefully handle the error.

Aleksey,

Your reply is not what I expected. For me, for us, you are kind of the official spokesman of the devteam here on the UT.

There were essentially two questions.

1) If it is true that the regular Save feature of the new Excel produces an incompatible file format, and if an existing Visual FoxPro-application uses IMPORT to import such an xls-sheet, then that existing app will gonna crash, right?

Your answer to this one is not constructive. First, even a graceful error and exception handler is a handler of nothing less than a crash and will oftentimes lead to the backdoor of the application, in order to prevent even worse damage. Second, I was not interested in your opinion about crash handling. I sought confirmation of what has been reported. I wanted to find out whether the devteam recognizes the incompatibility issue.


2) Are you saying here that the developer has no other choice than, either to change the code in the app, or to instruct the suppliers of the xls-sheets to deliver an older Excel file format?

This question got no reply at all. Moreover, the text was even removed from the reply, suggesting that it was not even asked. However, an appropriate answer to this question is important enough to us, professional developers.

Please, reconsider a more serious reply this time.