>Denis,
>
>There is a big, gaping hole in your comments...
>
>>Some replies will tell that it's good to add another tool to your toolkit when in fact this argument is bogus.
>>
>>The real answer should always be that the tool used should fit the job to be done.
>>
>>And in many cases VFP should still be that tool.
>
>So, in those cases where VFP is NOT that tool, you are out of the bidding, correct? With another tool in your toolkit, you have a chance to get that job or contract, so how can that argument be bogus?
>
>In fact, I'd say that in MANY cases, having multiple tools in your toolkit will open you up to contracts where multiple tools are required. (VFP and SQL Server, VFP and .NET, VFP and ASP.NET Web development, VFP legacy code and COM+ dll's, VFP and HTML, VFP and XML, VFP and Terminal Services or Citrix, VFP and Crystal Reports, VFP9 and SQL Reporting Services, etc, etc...)
>
>Don't ever stop learning unless you plan to retire soon. :-)

I still learn things with VFP. I'll have other stuff to learn with VFP9. I always learn new things. But the thing is that there are only 24 hours in a day. I learn stuff that I know will be worth it. To me VFP is still the best tool. That is for the things that I have to do. So until VFP meets my requirements I don't see a need to learn something that would have the POTENTIAL to PERHAPS be good for me in the future. So until then I let them fix things with their .Net thingie and keep an interested eye on it.

Who does'nt plan to retire soon? The real question should be Can I afford to retire soon? ;-)