I have watched with wonder the contining VFP and .Net arguments
going to and fro here on the UT.

Software development is problem solving. If .Net or VB6 or VFP 9
is the tool that solves that problem best, then so be it.

In my 20 years of development, most of my customers know nothing
about programming languages, let alone the differences between
the 2. I'v developed in various languages througg the years to
include GW-BASIC, QuickBasic, VB, FoxBase, FoxPlus, FoxPro, VFP
C++, and .Net. I targeted various forms of data; SQL, VFP, Access,
Clipper, flat files and so on.

I don't choose a langauge bacause its maker says its the best tool.
I choose it because it gets the job done best in that particular
situation.

Most of the time, if your an IS department guy, you use the tool
the company uses. If your independant, you use the tool that best
accomplishes the job.

You could line up 1000 people who could come up with reasons why
.Net is better than VFP. And you could line up 1000 people who
could come up with reasons why VFP is better than .Net.

So, having said all this, can we finally put this to rest here on
the UT?

Like Rodney King said, "Can't we all just get along?"