Paradox 7: Index out of date

[Gerard Rokx]

Hello,

I get the error message "Index out of date" at startup of an application.
This occurs after an incorrect (abrupt) shutdown of the server.

Sometimes the error occurs also when I try to delete an entry.

In this application I use Paradox 7 and Delphi 2.0. The Paradox 7 files are
created with Database Desktop version 7.0.

Why does the error occur?
Can I solve the error in an easy way?
Can the error lead to corrupt data?
If possible I want to solve the error directly when the application starts,
or create a seperate utility for it.

Thanks,
Gerard Rokx

[Søren A. Kolind]

It is not that hard.
When creating a index, be sure the "Maintained" option is checked.

/Søren.

Gerard Rokx <gerar...@tref.nl> skrev i artiklen
<79tvt9$gd...@forums.borland.com>...

[Sundial Services]

Gerard Rokx wrote:
>
> Hello,
>
> I get the error message "Index out of date" at startup of an application.
> This occurs after an incorrect (abrupt) shutdown of the server.
>
> Sometimes the error occurs also when I try to delete an entry.
>
> In this application I use Paradox 7 and Delphi 2.0. The Paradox 7 files are
> created with Database Desktop version 7.0.
>
> Why does the error occur?
> Can I solve the error in an easy way?
> Can the error lead to corrupt data?
> If possible I want to solve the error directly when the application starts,
> or create a seperate utility for it.

"Index out of date" occurs when one of the files, the index-file, is
"one step behind" the DB-file. A change is made to the DB but a
corresponding change to the index-file failed to happen. Unexpected
application shutdown or a network error is the usual cause.

While "index out of date" is by itself benign, the general problem that
leads to "index out of date" can also lead to more serious problems
including corrupted data. The problem is that each update to a database
is a series of disk-writes, and if some of those writes take place while
others do not, you can see that potentially "anything can happen."

Index problems are not a normal occurrence - their root cause should be
closely investigated and solved. However, they do occur often enough to
warrant having a tool to quickly and easily fix them. Database Desktop
does not furnish such a tool.

The traditional solutions are based on "TUTILITY" or "TUTIL32." You can
download a simple tool from the BDE pages
(http://www.inprise.com/devsupport/bde).

And we sell the world's only(!) tool that can go beyond what TUTILITY
does, in terms of both capability and speed.
http://www.sundialservices.com/cs3web.htm

[Mike Ver Hagen]

To add to what Søren reported, you may note that in order to select
"Maintained" for a secondary index, you must already have specified a
primary key. mIKE

[Bill Todd (TeamB)]

Indexes and the table itself can become corrupt due to either a workstation
or server crash. You can use the table repair program on the Inprise Web
site at www.inprise.com/devsupport/bde/utilities.html along with the version
of TUTIL32.DLL for your BDE version to repair the table.

Bill

--
Bill Todd
(Sorry but TeamB cannot answer questions received via email)
(Remove nospam from my email address to contact me for any other reason)

[Don Gollahon]

Another Great table repair utility that is FREE and can even repair a whole
directory of tables is B&P Table Utilities at http://www.bpsoftware.com/ .

Gerard Rokx wrote in message <79tvt9$gd...@forums.borland.com>...

>Hello,
>
>I get the error message "Index out of date" at startup of an application.
>This occurs after an incorrect (abrupt) shutdown of the server.
>
>Sometimes the error occurs also when I try to delete an entry.
>
>In this application I use Paradox 7 and Delphi 2.0. The Paradox 7 files are
>created with Database Desktop version 7.0.
>
>Why does the error occur?
>Can I solve the error in an easy way?
>Can the error lead to corrupt data?
>If possible I want to solve the error directly when the application starts,
>or create a seperate utility for it.
>
>

>Thanks,
>Gerard Rokx
>
>
>

[Thomas]

Hi Gerard,

I worked on an app with Delphi 3 and Paradox 7. I had used the
CachedUpdates mode, the transactions and the referential integrity. I had
this problem everytimes.
As soon as I was doing anything with the data --inserting, updating or
deleting, I had the "index out of date" when I launched back the
application.
There is no solution to that problem if you demand the above
functionalities !
The first thing you can do is to take off the referential integrity from
the database.
The second is to take off the transactions and the third, the cached mode.

There is a tool you may find on
http://www.borland.com/devsupport/bde/ti_list/TI3342.html to repair
corrupted tables and you may get informations about different issue met
with Paradox 7 and Delphi --for instance, the local share parameter in the
idapi.cfg
As for the abrupt shutdown of the server, as transactions on Paradox won't
rollback in this case, I don't think there are any ways to avoid it ;
anyway, all I told you above should clear the problem.
Hope this helps.
Regards.
Thomas.

Gerard Rokx <gerar...@tref.nl> a écrit dans l'article