I can't find Walter's post that I read earlier, so I'll respond to yours.

He made a statement that shows his lack of understanding of anything other then VFP. Something along the lines of how "data-driven" his apps are. Insinuating that this feature requires VFP.

Don't know about you, but I've seen many Java/dotnet apps that are highly configurable. They have no problems storing the data necessary for config purposes in XML files. I'm working on a Java app right now where we have started adding some features using the Spring framework. The whole purpose of Spring in Java is to allow for a highly configurable app. Including defining which class to load based on the XML config files.

>The point is, there are many more circumstances where VFP does make sense. This is one of them and by itself proves the ignorance of your statement. You're looking from your own little perspective which has little to do with the world outside. VFP never played a significant role in the big corporate world and implying its dead because of its decline up there is silly. It is in the mom-and-pop applications where VFP still will be significantly present.
>
>"Ignorance"....hmmm, all this coming from someone who stated that VFP handles design patterns better than .NET because of the way it works with data.....from someone who openly asserted VFP developers' right to arrogance as the only enlightened ones when it comes to working with data.
>
>I don't say or imply that "VFP is dead" because I don't talk and think that way - you're putting words in my mouth. What I have been saying is that it's been on a downward trend for several years, and conversion projects continue to mount. Yes, a few go from VFP to Java/Oracle, but most go to .NET/SQL Server. Sure, VFP apps will continue to be present for mom-and-pop apps. The same could be said for VB6. Maybe even some Delphi and QuickBasic and Clarion applications. So what????
>
>Walter, this "best tool for the job" argument (as it's been presented here) isn't sharp. Expecting it as the only appropriate response to every scenario has become an almost knee-jerk expectation. It reminds me of the ubiquitous question on employment honesty tests: "If you saw a co-worker stealing a dollar bill out of a cash register, would you immediately rat them out?" Those who respond with anything other than "yes" are potentially viewed as dishonest.
>
>Walter, I've worked for the feds, state govts, large companies, medium ones, and yes, small ones. I don't like to start making comparisons, but I'm guessing I probably have a little better breadth of experience than you - and a better concept of all the characteristics that go into the word "best". "Best" also includes business considerations - I know companies that have not won contracts ONLY because their products/services were specifically VFP-based.
>
>I'd said my two cents. You can have your numerous and diffuse mom-and-pop shops, and JR can have his QuickBooks app.
>
>Kevin