Bonjour Jean-René,

>Where you are wrong is that you think that you do not have the time to learn another language. I know because I use to think the same thing.

My problem here is with the level of expertise that somebody has to acquire with the other languages.

I already learned other operating systems, programming languages, specialized software and here are some of them: DOS, Pick, UNIX, Windows 95, Windows 98, Lotus 123, Microsoft Excel, Microsoft Word, variants of assembly language (Z80, 6502, 8088), variants of BASIC (GWBASIC, QBASIC, Pick Basic, Model III BASIC), variants of batch languages (MS-DOS Batch, Proc (Pick batch language)), C, COBOL, Clipper, Delphi, Turbo-Pascal, VFP ... and others that I forgot about.

The thing to understand here is that because I don't use those tools as often as VFP I forget more and more on how to use them efficiently. I'm sure that I could pick up fast if I decided to come back to one of these tools but this in another part of the problem (remember the time factor) and I don't see the need to go back to those tools.

Fox example I am sure that for big number crunching it could possibly be better to make VFP interact with Microsoft Excel. The big problem here is that I will probably have to read about all of the functions that are offered to me by Excel. You understand that if I already made the decision to go to Excel it would be better to know what are the best functions offered to me. So now I have to sort of master Excel so I know that I will make the right choices when working with VFP and EXCEL.

You can apply this to almost everything that you do. Always wondering if you are using the right tool.

So with the kind of work I do right now (mostly local database processing) I will continue using exclusively VFP. I will be preparing myself for SQL-SERVER eventually with MSDE. "I will cross the bridge when I get to the river"


>Denis, if you have the time to reply to this thread you do have the time to learn other language.

You see Jean-René it is good for my mental health to come here and engage in discussions now and then. There are many hours in my days devoted to learning mastering and working with VFP. I consider my UT time as being a good way to kind of take a break from it all.


>>So maybe I will be wasting time by using VFP for everything but maybe the evolution of VFP will justify me staying focused only on that product.

>Maybe you thing so, but you are wrong. You need the best tool for the job. Has a developer you must get the best tool or write it if needed.

Now you know what I think about this.


>>I've heard that VFP is the best tool to work with XML (because of string processing speed). XML is suppose to be a big part of the internet future so maybe after all VFP is not so bad...
>
>VFP is not the best tool for XML. VFP is the best tool for XML when you have to use VFP data. XML is a tool, a way to exchange information, so the best tool to use with XML depend with what other technology are you exchanging information to. VFP will not be the only technologies use.

I can't argue with you on this. I only heard about this. I don't know XML but are you really sure about this? If VFP is not the best tool what is the best ?