>>Foxpro/DOS has reached the end of its lifecycle. VFP has not (right?). That's why it is not the same issue. What I suggested in my reply (you may have missed that, because I wrote that in an update), is that it is made clear that it is rather only the IMPORT command that has come to the end of its lifecycle. If that is confirmed, then I suggest this is explicitly stated in its documentation with the next SP.
>
>I think you're attempting to split a hair that can't be split. FoxPro *IS* at the end of its lifecycle.
>
>So was Clipper S/86 many years ago, but our customers are still running applications written in it. They don't complain that it can't understand XL8 or XL5 files.
Well Dan, your *IS* is nothing more than your *OPINION* or your *PERCEPTION*, isn't it? You are not an employee of MS. I have, up till this day, never got any clue from any MS employee, not even informal, that vfp *IS* at the end of its lifecycle.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
