>>>Now, what I'm asking is whether or not it is true that vfp's IMPORT command will fail for Excel 2007 files that have been produced with the normal Save option. And if that is confirmed, whether or not it is regarded as a compatibility issue. Yes?
>>
>>Peter, I also have Office 2007 and think the Office team has chosen to do a big no-no for their customers. From what I can see, in Office 2007 the default format for the save is xlsx, and it seems a user cannot choose a different default, such as xls (this is what I consider the no-no.) They are taking a page from the VB team and ignoring backward compatibility. Frankly, except for the fact that I wanted OneNote, I am sorry that I upgrgaded, and to Ultimate ($$$) too.
>>
>>In contrast, the VFP team has always tried hard not to break previous code, even to the extreme of leaving what might be considered "erroneous" behavior that some developer might be counting on. I am thinking of REPLACE OtherAlias.MyField, which fails if EOF() is true. As you know the VFP team provided REPLACE MyField IN OtherAlias as workaround. That is acting responsibly. I believe the VFP team has acted *very* responsibly to VFP developers, and think it is unfair to suggest otherwise.
>
>Alex,
>
>You are right, as I see it, on both points. And indeed it would be unfair to suggest the VFP team has acted irresponsible so far.
>
>Having said that, are you suggesting here that I have suggested otherwise? To be clear about this, I think the VFP team indeed *has* acted very responsible. And I'm now trying to find out whether that will be case in the future also.

If you want to know the truth, I think you were frustrated and blew at Aleksey, but you already gave proper credit to the VFP team so I suspect they understand. We are all on the same side.

Alex