Now I honestly don't know if they were or not, I do know that the results of the test, won our organization a great deal of funding for FoxPro development, and of course a benefit or two to me in a financial sense. I would hate to be shadowed by the thought that it was a bogus test. But I will rest on the fact that I did not write the test or the query's.

What is did for me was to make me take a longer look at the data structures and formats of the database products sold by the "big boys."
But I do have to remember that the majority of database applications are not on a VSL (veryLarge Scale) dataset, and hence VFP is still a contender in this arena, even though there is little support from Microsoft, as well as the book writers, etc that will assist in training new developers and certifying them.

For small scale database products, of course there is access, Visual basic, or most any programming language that can handle COM objects.

Now if We could just ger a FoxPro Front end talking VIA tcp/ip to a foxpro back end - we could recover the lost functionality and abilities of our migrated applications to the Web. West Wind is a good tool, and So is Allaire's Cold Fusion. Interdev, I guess, works, but is hard to learn, hard to use, and somewhat kludgy. Who decides which tool to use? Well in the corporate environment I work in, it is the tool that provides the solution for the customer. Programming languages cannot continue to be considered a religion, nor can one succeed in their careers only knowing how to use one tool. At least that is my opinion.

Meanwhile our company needs three new full time FoxPro application developers.


>Was the SQL data properly optimized? Were the queries on both sources exactly the same? Are you sure that the VFP data wasn't using filtered recordsets?