>>> That's why I'm wondering what customers do that upgrade applies to?
>>
>>Denis;
>>
>>If you upgrade to VFP 8, simply inform your clients that you will do all future fixes or add on requirements in VFP 8, and have to charge them for the additional work involved to make code changes, debug, and re-compile . Microsoft is looking out for all developers. You will automatically have people pounding on your door the day VFP 8 is released, “I want my application re-done in VFP 8.0”! Watch out for the rush and I hope you can handle the extra work.
>>
>>At the same time for those third party add ons that will not work with VFP 8, that will help the industry also. You will have to purchase new upgraded add ons and that will provide additional revenue for the companies involved. This is truly a win-win situation. :)
>
>I just hope that it's going to be as easy as you say.

I do believe that you could code and compile in VFP8, and it will still work using the VFP6/7 runtimes. At least as long as you don't make any use of any new VFP8 syntax or features.

Word of caution about that. If you build an .EXE, you'd have to explicitly start it using the VFP6RUN.EXE or the VFP7RUN.EXE else it will be looking for the VFP8 runtimes if you just start it from Explorer.