Sam

To make this decision you also need to look at how you will implement your future work. Will it be windows client server / local work, or will you be writing for the web?

Also, you need to assess the relevance of various advisors comparing their needs to your own and weighting their conclusions.

When discussing such items, the tendency is for various pundits to laud "everything about their preferred tool" even when it is clearly deficient.

Eg: take a look at

http://www.devx.com/free/hotlinks/2000/ednote092000.asp

I quote:

"To bring home the importance of the VS.NET migration, Green admitted deficiencies of Visual Basic 6 for Web application development, saying, "Somewhere in the back of your mind or perhaps right in your face screaming at you is this voice that says 'we can do better. We can build a better class of tools and we want a better class of tools."

This is the reality, but it is hardly what we have been told by VB pundits who have waxed lyrical about how great VB is, including for the web. The fact is that if VB could do any where near as much as (say) West Wind, the huge changes for NET would be far harder to justify.

As long as there is a migration path, I would not worry about VFP vs VB. I would focus more on "web vs windows UI" if I were you.

Regards

JR