Hi Peter,

>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.
>

Thank you for confirming this, I'll keep this in my mind.


>I sought confirmation of what has been reported. I wanted to find out whether the devteam recognizes the incompatibility issue.
>

Define a crash, Peter. Is it an unhandled Win32 exception or an unhandled VFP error? The second is likely if the app doesn't use proper error handling. The first potentially might happen, I don't have a proof that it will never happen.


>
>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.
>

OK, I will leave this nonsense here to avoid additional accusations, but I am not going to reply or comment on it.


>However, an appropriate answer to this question is important enough to us, professional developers.
>

What I am saying, Peter, is that there are no plans to enhance IMPORT command to support new file formats. The choices that you've listed here should work. Whether these are the only choices? I don't know, professional developers may find some other choices.


Thanks,
Aleksey.