I thought you wrote your own compiler so your compiler can't as fast as like VFP because of issues like Rushmore Optimization. So there just one risk for me stability. You spent your months for this. If there will be a strong version, I'll buy this. After you send my invoice, I don't care anymore, this's a issue with you and MS...

>Hello everyone,
>
>
>> How is this possible, have Microsoft released the VFP source code?
>
>There is no the C source code, so to fixed some bugs or added some Advanced functions, it is difficult.
>
>
>> No, they haven't. All it takes is a decompiler and a lot of time.
>
>Usually, it is, and it need more than 30 months,
>please refer to:
>http://www.baiyujia.com/vfpadvanced/f_vfpa_history.asp
>
>
>> Did they properly handle key sizes? how ints are stored? If they changed those, then you need to convert all your tables and reindex and you won't be able to access the data from 32 bit apps. Merely moving to 64 bits doesn't mean you can get tables bigger than 2 Gig. And at that point, the advantages of 64 bit are questionable.
>
>I will try to do some changes to support > 2 GB files.
>
>
>> If they decompiled the VFP.exe and built their compiler, they've done it illegally. Microsoft still owns the copyrights.
>
>Why to develop the VFP Advanced, I think everyone has known that:
>http://msdn.microsoft.com/en-us/vfoxpro/bb308952.aspx
>
>There are some law problems for the VFP Advanced,
>so I said:
>VFP Advanced = VFP 9.0.0.7423 (SP2) + VFP 9.0 Fixes, it is an unofficial service package,
>VFP Advanced is FREE,
>and I have not changed any copyright text, for example (c)Microsoft.
>
>Please refer to the thread on foxite.com:
>http://www.foxite.com/archives/is-vfp-c-compiler-illegal-0000390387.htm
>
>
>> Beyond that, I have no idea what the VFP++ compiler does. He may just be turning the P-Code into commands that make direct calls to the VFP runtime.
>
>Yes. Usually, it can call _Execute() and _Evaluate() API to run VFP p-code.
>
>I think there is no problem for the VFP C++ Compiler,
>it can translate VFP code to C code, and then compile the C code to a VFP API library (.fll).
>it is a VFP protect tool.
>
>
>> It's possible that the law is different in China and would allow this. But Microsoft has been cracking down on software piracy there.
>
>Really, I do not want to violate the Microsoft's EULA,
>I always think Microsoft is a great corporation,
>and thanks them shared some data, for example, many Windows APIs on MSDN.
>
>But they kill VFP, I think it's a bad thing, but we can't change it.
>
>Only for VFP, I only wish we can get a FoxPro 64-bit program,
>I will not do same things for other Microsoft products.
>
>
>Best regards.
>
>Chen
>2015.3.10