General information
Category:
Coding, syntax & commands
>Whenever you set filter you need to...
>1)Ensure that you have an index on the field you are filtering
>2)set order to 0, otherwise you essentially get 2 filters fighting each other
>3)if you have set deleted on, you should have an index on deleted(), something like "INDEX ON DELETED() TAG ISDELETED"
>
>In most cases it is better to use an SQL Cursor for most filters.
Hi,
Thanks, but this doesn't help. Maybe filters are supossed to be that slow. I have found a good solution (without a SQL Cursor). Instead of a filter I use a master table (for the organisation button) which is linked to my main table (as child). With a little coding also the navigation buttons work well. This method is very fast: more than a million records are no problem.
Andreas
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only