>Randy,
>
>As long as your view is at least partially optimizable VFP will not bring the whole table over the wire. It will bring as much of the index over the wire as is necessary to process the query. It will then bring as much of the table as it has to over to satisfy the results of the query. There's certainly more traffic than with SQL Server, but much less than if the entire table had to come over. The key is to make as good use of indexes as possible to ensure that most of your queries are at least partially optimizable.
>
>>We are considering the best solution for a 125 plus user VFP app running on 100mps NT network. The client isn't ready for SQL Server at this time but will be soon. The question is this...what does VFP send over the network when you use a parameterized local view? As with any query, VFP opens the tables used by the local view. Does the whole table come across the wire?
>>
>>We are wanting to write the app using local views running against a VFP 5.0 database on the server. Speed and reliablity are a must.
>>
>>Any expertise or ideas would be greatly appreciated!

Thanks,
I was under the same impression. Is the risk of corrupting indexes, upon a network or work station mal-function, the same using local views as compared to using buffered tables? Do you have any preferences as to the best method. These users will be hitting a 900K record customer file and manipulating account transactions.