>
John, are you a VB developer now?< G > I thought you were a developer who used the right tool for the right job.
<

For single/two-tier development, regardless of whether it is Fox Data or SQL Server Data, I use VFP. For n-tier and web-based development, I am more apt to use VB since these development efforts are more component based. Components are easier to development in VB. The footprint is lighter. The ability to make use of events, collections, and user-defined types is of paramount importance. That is not just my opinion, that is fact.

I have come to the realization that many cannot handle the cold hard truth. Of course, it begs the question of why it is difficult to take. To me, it is not a big deal. How people get easily offended is beyond me.

Life's too short. I have no time to deal with the narrow minded among us..< s >.


>
I think you make a good point that we should use the right tool for the job. It's just that so many have invested so much into learning VFP while MS pulls the rug out from under us. It's like the scene in the movie Mars Attacks where the Martians are saying "come back I won't hurt you", all the while firing lasers at the people. I continue to use VFP and will for the forseable future. Heck, maybe Rick Strahl will form a publicly held company, which we can all invest in, buy VFP, and then kick the crap out of MS!
<

How much time do you think I have invested in VFP? I have two books, scores of articles, thousands of hours of reaseach and development, etc. The transition to using different tools is tough. Yes, we invest tons of time and money in learning tools only to have them become obselete. This is the business we have chosen. As Jim Booth says, if you want a career where nothing changes, go dig holes. The same basic technology has remained unchanged for the past few thousand years.