[tpfkanep]

Hi,

I receive the following error when trying to run an application that uses Paradox .DB files:
"Index out of date. Indexname"

What does this mean and how do you resolve this?

Regards
Nicholas

[dlatner]

When you create an index, you select if it is automatically maintained or not. It might be that this particular index was not. It shouldn't affect the table, except for the speed of searches and sorts. You can either reindex the table or delete the index.

[tpfkanep]

Hi,

Thank you very much for the advice!
Application is working.

Regards
Nicholas

Originally posted by dlatner
When you create an index, you select if it is automatically maintained or not. It might be that this particular index was not. It shouldn't affect the table, except for the speed of searches and sorts. You can either reindex the table or delete the index.

[sundialsvcs]

Originally Posted by tpfkanep

I receive the following error when trying to run an application that uses Paradox .DB files:
"Index out of date. Indexname"
What does this mean and how do you resolve this?

Assuming that the index is "maintained," as is normally the case... Paradox uses a change-counter byte in the header of the DB and of each index-file to make certain that, when the table is updated for any reason, all of the indexes are updated to agree. If the header of any index does not, "index out of date."

In our experience (and we've been dealing with specifically these issues since 1996 or so), the most common cause of this problem is a problem in the networking software on one machine or another (usually an older machine running an earlier version of Windows than the rest); or a problem with the BDE Configuration settings. Either the workstation is not using the same Configuration file, or the NET FILE DIR setting is not the same as with all other machines.

If someone is using Paradox on the same computer that is also hosting a shared database, and the LOCAL SHARE setting on that machine is not TRUE, then there will be certain and swift grief because that machine won't obey the same locking-protocols that the workstations are using.

If a Paradox problem happens "suddenly," don't overlook the serious possibility of an un-diagnosed network error. Believe me (because it has happened here too), a port or half-a-port can go out on a piece of hardware and the lights still blink. A wire can become loose in a cable if it passes under the wheels of the secretary's desk. Attach too many devices on the same office electrical circuit, drop the voltage on the line down just a couple of volts (the lights won't even dim), and .. grief. If a problem "crops up suddenly," absent a recent operating-system update, it's almost certainly hardware.