>However, the filter will not be Rushmore optimizable in a grid. So if you have a lot of records, using a filter on the RecordSource of the grid will be slow. You would be better off to use a paramterized view.
>
>Marcia
Hi Marcia,
I'm trying to compare SET FILTER and parameterized view... I have a table (over 100K records) of sales reps, their customers (just customer numbers), effective dates, as well as end dates, assuming sales reps (if the sales rep relinquishes the customer), and active flag. About 1/3 of the table are active with blank end dates & blank assuming sales reps. The rest are inactive with end dates and assuming sales reps.
An user enters a sales rep in a form and selects "active" or "history". A grid appears with all customer numbers for that sales rep. Can be anywhere from a few records to hundreds, but there are a couple sales reps who have over a thousand. When the user enters assuming sales reps to some customer numbers (a sales rep relinquishing some customers to another assuming sales rep), there's a method that updates the end date and active flag to inactive as well as add new record for the assuming sales rep to be the active rep of the customer number.
OK... I created a form using the actual table with SET FILTER, with a relationship to the customer table (read-only) for customer names. It works fine. I have a direct access to the server (using VFP DBC) so speed is not an issue for me but my concern is for the remote users who depend on WAN across the country. So I researched UT and concluded that a parametrized view would be better. I re-created another similar form using a view instead of SET FILTER. Making one change works fine but the more changes to the grid and clicking save (view's buffermode is 5, and cmdSave fires =tableupdate), the more "Running query...." loops. Makes me wonder about views... the larger the table is, the more changes to a view, the slower it is (and the more often it requeries). Am I right? In this such situation would SET FILTER be better? How can I avoid the REquery for every record changed even tho the buffermode is 5? Why can't the view be updated at one time?
TIA...
Thanks!
~d
J