Hi Richard,

I cannot recall where and when, but I have read many times that SET FILTER is not the way to go, and that you can face performance problems. Your tables are not big and they should work OK. Try to crate indexes on you common filters to see wether it improves performance.

If your system is going to grow, I'd make a rewrite of this part of the code and start using views. If there are many user updating the system at the same time, try to put the views on a local (by user) database to avoid contention: when opening a view, VFP blocks the database file for an instant, and if many users are doing the same performance may be hit.

>Hi All,
>
>Packing and Reindexing is done at the end of every day.
>
>The network is protected by up-to-date antivirus which has not reported any attack.
>
>SELECT is not an option as there is need for updates. Views could do yes but it still does not explain to me why this is happening all of a sudden. Is it something to do with the sizes.
>
>Network speeds are 1.0Gbps. Larget table is 30,240KB with Records: 249,710. Fields: 18, Length: 124, Index: 2. This table is also the most dynamic in terms of deletions, insertions and updates.
>
>Regards,
>Richard
>
>>I would get rid of the SET FILTER ... In the long run you will save headaches. Try making SELECTS if you only need to view data, or working with views if you need to update it; both are fast and responsive over a network, and you won't face performance problems when the tables grow.
>>
>>
>>>Dear Saviours,
>>>
>>>I have a situation that requires a solution urgently:
>>>We have a database situated in a Winows 2000 file server. About 25 users access the various VFP tables from their WinXP or Win2000 stations. Their mode of access is live browsing on the tables. Majority activity include viewing of records as results of a SET FILT command given from the command windows. The tables are of varying sizes. The largest has abut 250,000 records.
>>>
>>>For about three weeks now, we have witnessed a decay in access speeds. The database has been confirmed to be valid but for some reason, on and off, psecific users suffer extemely slow response to the SET FILT command or any other access. This is so much so that at times it ends in the users PCs hanging.
>>>
>>>So far we have confirmed the the problem is not localized to the PCs at the workstations. We have also confirmed that it is not tied to network or local user profiles. Different users at different times tend not to be able to work.
>>>
>>>Anyone: Kindly give us pointers of where the problem is. It has been OK for almost 5 years and it is the first time that we are experiencing this. Is it something to do with FoxPro share limits? The data is growing...
>>>
>>>Regards,
>>>RN