>No one can bring any substantial evidence of a prejudice; and any civil case requires you can prove à prejudice.

Copyright cases are often tried as criminal cases, not civil. And there you only have to prove a violation of a law or contract. In these cases, it is cut and dry that what Chen has done violates the EULA. The only question is if the EULA is in effect where he is, and even if it isn't, if it's still in effect where the rest of us are where we would obtain his derived work and apply it to our copy, which we are under EULA restrictions for.

>The reasons you enumerate are far too hypothetical IMO

There's some reason Microsoft abandoned such a powerful tool. I've always believed it was because only the developers had to purchase it. They wanted something that every end-user had to purchase (from Microsoft). With the royalty-free runtime distribution, it just didn't work with their money-focused model.

I believe another reason was because they could not integrate VFP into .NET because it hampered performance so significantly that it would've highlighted juts how poor .NET is compared to native Win32-based apps.

So, Microsoft wanted money, and they didn't want the stain against their flagship technology which would hinder them having that money.

>>>There’s no IP case without a prejudice; MS can claim none.
>>
>>That's not true, Theirry. Patents and copyrighted material are bought up each day and then shelved so no one can use the material and therefore compete with another product. It is their in-the-court / as-a-company legal right as the IP holder.
>>
>>MS can claim prejudice because they are the copyright holder of the content, and they made the choice to abandon their software for strategic purposes (to require people to buy SQL Server, or switch to Access or something else).
>>
>>By extending the life of VFP9, they can claim that it hurt their business with regards to Access sales, or SQL Server sales, or whatever other goals they had in mind when they dropped such a powerful tool in favor of their .NET-based platforms and future.