>>>>>>One thing you can do is to reduce the amount of data fetched over the network. For instance, with parameterized views.
>>>>>
>>>>>Hey I have a question about this.
>>>>>Local parameterized views VS. Remote parameterized views.
>>>>>
>>>>>If you have VFP tables in a .dbc and use remote views to access the data, is that going to generate less network traffic than using the local views? Anyone ever done any testing on this??
>>>>
>>>>The only difference between local and remote views is that remote views use ODBC or OLE DB drivers, in which case they are slower.
>>>>
>>>>Because DBF's are not running in a Server environment, you will not get any difference in network traffic.
>>>>
>>>>Kev
>>>
>>>But doesnt a local view acutally require that the table be opened and remain open while the local view has it...?... unlike a remote view where this isn't necessary?
>>
>>Yes, but that won't affect the speed, the only performance hits are when a view is querying and updating it's table(s).
>>
>>Kev
>
>Hmmmmm... well ok. How about this...
>Since the table itself must be open when using a local view, the server will have a lock on that file (so you can't get exclusive use of the table) while the local view is open.....
>But you won't have this proglem with a remote view? Is that right??

I'm not entirely sure, it may be worth checking. It depends on how the ODBC/OLE DB drivers work, I imagine that if you open a remote-view it would keep the tables open (in another memory space) rather than keep open/closing the table(s).

Kev