Hi Dave

One solution, if you need large quantities of data, is to only go once for the majority of it and store it locally (in updateable cursor) and go back periodically for updates/refresh from a paramaterised view. In effect you are performing local caching.

This can be used in place of true Client/Server where an interim fix is needed or the cost of redevelopment is prohibative.

What you may notice with your current system is that it is relatively fast until someone modifies the table(s) you are using and then performance dives.

I dont know why this is.

Regards
Geoff Scott

>I have an application that resides on a network share. All the data is on a network drive in the same area as the .exe. The users have shortcuts on their desktop to start the .exe. In addition, the runtime files are in the same directory as the .exe. The application has forms that run private data sessions and use local views to access data. Lastly, the application opens all the tables when it starts up so that when the user opens a form, there is much less overhead because, as I understand it, keeping the tables open in the default datasession means that vfp issues a use again instead of a use when accessing the table via the local view ( this is born out in my testing ).
>
>Here's the rub
>
>a. I notice approx a 5x faster performance on this app when I run it locally with local data
>
>Can any of you suggest configuration or engineering changes in my application to address this performance issue. I'm starting to get inquiries about this and need to make some changes.
>
>Thanks.
>
>Dave