Peter,

Sorry, I couldn't get this out sooner.

I re-examining my post to John which you mentioned, I've come to the conclusion that when I used the word "enviable", I probably should've qualified that by a reference to my own work. For me and the needs of my "customers", I'm going to be able to meet those needs in a variety of ways. For someone else, with a differernt set of requirements, it may not be so "enviable". We all (or at least most of us, your's truly included) tend color things based on our own set of circumstances and/or prejudices. This certainly was the case with my original post.

Now to give you an answer regarding what direction you should take, I'm going to pursue a slightly different avenue. I'm not going to say, "Stick with VFP". Neither am I going to say, "Jump on the .NET bandwagon". I will say that I'm going to be looking closely at VS.NET. Fact of the matter is, that anything we say regarding either is strictly speculation. Could .NET fail? I suppose so. Business history is littered with well-hyped failures. Remember "Microsoft Bob"? "New Coke?" Frankly, I doubt that it will, but that's just an opinion and it and 50 cents will get you your local newspaper.

I'm am going to say that whatever direction you take, learn well and apply the fundamental principles of programming and programming techniques. What language? I don't see that as relevant. The principles apply across languages. Basically (no pun intended), programming is about solving problems, and the language is simply the tool you implement the solution with. No more, no less.

John was very correct when he made the statement, "I am not my tool". That's my take.