>>I'd like to stick with VFP as much as possible. I want to learn things that go with it, like SQL Server, but I'd rather be really good at VFP than a little good at a bunch of things. We'll see how things go. If I need to learn something else, I will.
>>
>>-Michelle
>
>I hear you. It is a VERY GOOD idea to master one tool before pursuing another.
>I first learned OOP when I bought and learned PowerBuilder on my own. What was
>a big surprise to me was that when I got into VFP for the first time, all the
>stuff I learned about OOP was easily transferable to VFP - only VFP was so
>much better! Learning a new tool is fun and adds spice to life, not to mention
>opening up more doors to contracts!
>
>Later

I worked on a similar basis. Started with COBOL, moved to DBase!! Had to learn VP Info (anybody remember this) because DBase didn't handle low level stuff. Then went to FoxPro. Employers bought a Unix box with incomplete software so I had to learn C for file conversions. Wrote some decent apps in C. Continued with FoxPro. Then FoxPro for Windows. Then Visual FoxPro (WOW!!!!).

I tried Visual C++ (hate it) and also had a copy of Borland C++Builder (love it). I am now looking at Delphi. Have written some small apps in Delphi without using ONE native command!! (Identical to C++Builder) - just used application methods. Small amount of VB also.

I've just been pounced on by a competitor for good money. They secured me within three days of contacting me (two interviews in three days then they put in an offer immediately). It certainly pays to spread your knowledge.