The VFP runtime is licensed just as if you were to purchase VFP retail. However, things like SQL Server, Exchange, operating systems, etc are licensed only for development and testing purposes. A careful reading of the MSDN license is required to be sure you fully understand what is allowed and what isn't.

>
>That point is a very interesting one. If my job as a software developer (when I have my VFP hat on) is to create an end-user application that can be run with just the VFP runtime, it seems that I am not limited at all in my use of a copy of VFP that comes in the MSDN subscription (for the creation of that end-user application).
>
>In the scenario I have described, what constitutes "production"?