Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sloooowwwww find 1

Status
Not open for further replies.

jlockley

Technical User
Nov 28, 2001
1,522
US
Seeking a value in a field (ctrl z) on one of my computers has suddenly slowed to a crawl from a pretty snappy pace. I vaguely remember encountering this issue before and actually fixing it, but I can't for the life of me remember how. Suggestions for cause/cure would be appreciated.
 
Have you checked that the table (or table index) is not corrupt? Although not the best tool, check the table with the Table Repair Tool.
 
jlockley,

My first suspicion would be that the index is either corrupt (and therefore needs to be recreated) or it has been changed from maintained to non-maintained and the slow down is being caused by the fact that's being rebuilt before being used (this assumes, of course, that it's the active index on the table).

Hope this helps...

-- Lance
 
I will check and rebuild the index. Maintained/non maintained are new concepts for me. Can you tell me more? Thank you. JLL
 
jlockley,

Maintained indexes are rebuilt whenever any field value in the index's fields is updated or modified. Practically speaking, if you have a maintained index and add ten records, the index is rebuilt ten times.

As you might expect, this slows the update process (e.g. posting of a record), but ensures that index-based locates, ranges, and other activities are as quick as possible. Maintained indexes are best used in applications that involve more searching than editing.

Non-maintained indexes aren't updated when the table is. Instead, they're flagged as being out of date. When you perform an index-based operation on an out-of-date index, Paradox rebuilds the index before performing the operation. Thus, certain ranges, locates, etc may be slow the first time you perform them, but then they're as fast as usual--until the index is out of date again.

Non-maintained indexes can improve data entry, but slow research operations.

Both types are very useful for specific operations and most well-design Paradox applications mix the two, depending on the needs of the programmer and the users.

The type of index is controlled by clicking the Maintained checkbox when creating the index using the Restructure dialog.

Hope this helps...

-- Lance
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top