>That said - does it mean that a good VFP developer will necessarily be a good .NET developer? No - since perhaps the good VFP developer's knowledge is entirely predicated on teh "VFP Way" of doing things. That said - just because one may be a good VFP developer - it does not mean he or she is a good developer in general. Good developers in general can and will be productive in any tool. They find a way - that is what makes them good - that is what makes them productive. Remember - its the fiddler - not the fiddle.
Heh. Boy am I learning THAT lesson. Every day I am confounded by my VFP blinders, which often leads to wailing and knashing of teeth. It may be painful to embrace a product at the loss of an old friend, but embrace it I must. And eventually, the blinders peel back just a tad more, and I get used to the .Net differences.
A lot of very effective and proficient FPW programmers decided not to climb the mountain, to their loss.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
