> >There is a common saying in the cultures of all of the peoples of this world: "The Jack of all trades is the Master of none." >My objective in developing software is to deliver good products. My objective is also to deliver the best products I can, and to do this I (or people on my team) have to be familiar with many different technologies even if they are within the same language, IMHO you should find an appropriate tool for the problem at hand - even if it means another language, just like you will not try to hammer a nail using a screwdriver .. VFP (IMHO) is the best tool for data-driven apps, comparing it to VC++ or Delphi or even VB on a simple application (as you told Vinod)is just like comparing apples and oranges, VFP is not a general programming tool when it comes to data-base apps - I think VFP is the best choice, you may think something else, and it is a free world, and you can use what-ever tool you think best fit your needs this is not to say that I wouldn't be happy to see VFP run faster and/or with a native compiler, but there are other improvements of the product that are more important IMHO >Even if I were working in a team where each one has his specialty, there will always be too much differing opinion among the team members that will always result in a weak product. And then we have to hope that the team leader is a smooth talker. I think you are dead wrong on this - there will be different opnions,wheter the developers use the same language ot not - this is just a matter of a good project leader. when you write self-contained (encapsulated) modules, it really shouldn't matter in what language they were developped it is up to the project leader to co-ordinate the efforts into a complete product Arnon