>I have gone well above 200K records, and found that the TOTAL time to return ALL the records from the query was much faster in VFP. Unfortunately (or fortunately), none of my clients have ever asked to view 200K records at one time. For this reason, a buffered view of the data is sufficient. While VFP has something similar through Views, use is still somewhat sketchy, filled with work-arounds and complications. I have been working VFP exclusively now for 2 years, and have spend an excessive amount of effort working around limitations in the product.>

I have a VERY hard time believing that VB beats VFP in *ANY* data access category. Please upload some comparative VB and VFP source code that demonstrates this.

>
>VB makes development so much quicker and easier, it comes down to this: the clients can either wait a month longer for their product to be produced, or a few seconds longer for their query results.
>

Didn't you say that VB is faster?? Then where does that "few seconds longer" statement come from? I also have a very hard time believing "VB makes development so much quicker and easier". My Fox classlibs make me much much faster at creating VFP biz apps than any VB programmer could hope to be. *Maybe* in some specialized situations, all else being equal, a VB app would be done faster....

>This was clearly a loaded statement. The speed of VFP may be lightyears (which BTW is a measure of distance, not time) faster on queries, but load time, development time, and interface response time is _visibly_ much slower.

Load time is slower. No argument. But not a big issue if you mean IPL time. Development time??? I just will not accept this and no other decent OOP programmer would either. I also won't argue on the interface response time *in most cases*.