Rodney ---

It *can* be normal with a non-optimized filter on a table of that size. Why not create an index matching your condition and/or SELECT - SQL to grab only those records you need....better yet, a parameterized view.


>We have a system that tracks shipped packages on the internet. Currently the file that we tracking from has about 750,000 records. I set a filter to "ShpSts != "D" AND Date > (Date() - 14)". After scanning through about 30 - 40 records the machine appears locked up. We are running Windows NT Server 4.0 SP3 on a Pentium 233 with 256 Mb ram. If I wait about 3 or 4 minutes the machine frees up. Is this normal? Any ideas on how to correct?