>What you're saying is you're too lazy to improve your ability to be employed. You also claim you want .NET, yet your questions show you don't know much about it.
>

Not exactly ... i been a free-lance programmer for 7 years and never thought of being employed and there are many projects in my hand that havent completed yet. Just that i see no vacancy for VFP programmer in my newpaper.
If all talk .net, companys migrating, do microsoft will still support VFP ?
Improvement
VFP 6.0,7.0 XML support+more
VFP 8.0 Cursor Adapter+more


>
>>Hi all
>>
>>Why VFP cannot be VFP.NET ?
>>
>>1.Because of the DBF ?
>> -> IMO. Kill DBF use sql server
>There are several things that make VFP what it is, you'd lose many of them. In fact, a VFP .NET would look very much like VB .NET. Even if there was a VFP .NET, you'd have to learn something new. In fact, you'll have to learn alot of new stuff.

but at least i dont have to learn VB basic syntax and command

>
>
>>2.Not many programmers know how to write VFP ?
>> -> Where can i find a website that I can post "I use VFP"
>
>
>Umm.. You just found one. The Universal Thread is a website and you can post "I use VFP".

No must people know about this site

>
>>3.Is VFP sales not even in the top 10 or top 20
>> -> Kill all pirated VFP copy ...see 1 report to Microsoft :) (Same as movie nowdays )
>
>It is impossible to kill all pirated copies of any application. There is always a way around various copyprotection schemes.

Various copyprotection schemes dont not work in some countries

>
>>4.Because VFP can be decompiled
>> -> For me i dont care, i think is faster to write than to understand people source code (more challenging, learn more )
>
>.NET can also be decompiled.

Not like something well known like REFOX. Even a non-programmer i met know about REFOX