>Use VFP if:
>1.) If you need to leverage existing VFP code.
>2.) You need the benefits and speed of a local/integrated Data engine
>and, maybe
>3.) You have a need to not use the standard recommended .NET way either because you don't like following the "standard microsoft way" or because not doing it the standard way gives some sort of advantage, i.e. security, etc.
>They're probably many others, but, these are some of the big ones...
>
>>In a recent reply on a thread I complained on a specific topic.
>>
>>There must be situations where it's preferable to use VFP over .Net
>>
>>I don't use nor know .Net so I'm asking to you developers that know VFP and .Net to contribute to that thread.
>>
>>I'm sure that with enough replies Ken Levy could then be able to add that information on the MS site. What is interesting here is that that information could be added to the VFP and the .Net portion on MS site.
>>
>>I don't think that my idea would be rejected because it's been said many times that we developers should use the right tool for the right job. So this information would be perfect for all developers.

I just hope that this thread still have a value after Ken Levy's first reply.