Must be late here as I usually don't post stuff like this but I do have this observation which I'm sure is not new.

IMO, given what we know now, it would have been very foolish to start any major projects in any version of VB before .Net. Unlike VB6, VFP continues to enjoy strong support from MS if not from new developers. With that said I made the jumb to .Net sometime ago and I really see that as the future of devlopement on MS platforms. VFP will be around in one form or another for a long time but it's peak has been reached and now it's on a long slow road to obscurity. VB6, on the other hand, is dead.


>Hi,
>(This message is mainly to get your comments, but not argue)
>
>I have read your messages about VFP from alot of thread like Mom and Pop.
>I would like to ask few questions:
>
>1. Are you using VFP?
>2. If your answer is "yes" for question 1, which are you use VFP at?
>3. What do you think VFP should mainly for?
>4. Should I keep investing on VFP, or move? If move, what language you prefer?
>
>
>Something I feel so curious are:
>1. From the 1st day I join UT (5 years ago), I can "see" you are not support VFP. You always suggest us to move to VB, becuase you think it is the "future" development tool. However, I can see you always participate in VFP thread.
>
>2. Before this, you "think" VB is future development tool. Now, VB is "obselete", because no more VB7, but VB.NET. AFAIK, both are different technology, and not backward compatible. Instead, VFP3 is fully backward compatible and keep upgrading. So, what do you think about your previous messages?
>
>3. How could you know .NET is future development tool? Any sucess story?
>
>Thank you for your attention. My english is not good, so pls forgive me if my message make you feel uncompfortable.
>
>
>Thank you