>SOS Folkes!
>
>I have a multiuser system that is becoming too slow on searches and saving. The database is setup with code implied relationships. However, this is not the problem because, for example, there is a simple screen that looks only at one table that has around 52,000 records. It takes about two minutes to search and another three to save!!! I have tried packing, reindexing... to no avail. ANY IDEAS?
On my system, a table with that many records is usually on the child side of a parent-child relation.
If you use a view (with parameter) instead of a filtered table, everything should work much faster.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)