>Hi Mike,
>
>First, try using a parameterized view and see the difference. Better yet, try this (are you listening Ed?):
>
>If you don't have one already, create a table with one million records with an integer primary key and some text fields (create indexes on the parameterized fields) and fill the fields with data. Then create a p-view which will return as many records as you want. Set the parameter(s) and REQUERY() to fill a grid.
>
>Then try the above with xBase and get back to me with your findings.
>
>Second, and most important, is that it's easy for many of us to rely on xBase at the expense not learning how to effectively use SQL. As a result, many of us would be hard pressed to develop a C/S application should the opportunity presents itself. This is the point I'm trying to make. Being well disciplined in SQL allows you to create C/S and non-C/S apps with VFP, but not both.
>
>Having a background in xBase gives us an advantage over other developers in that we know data. But we can't rest on our laurels, we have to go the extra mile or become another fart in the wind.
>

Your reply had nothing to answer the simplest question why SEEK() is bad. If you are interested to know something about your own example, well I can give you a clue: X-Base approach will work faster if number of records in recordset is less than 50. It does not mean that p-view is bad, but it just illustrates that before branding labels you may better learn something.
As you probably understood already, my experience in C/S applications is extensive enough. I'm not going to compare it with your (someone else one) experience, it's not my business to evaluate other people. I think your posts speak themselves.