Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: Borland App Server
Expertise: Beginner
Apr 10, 1998



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Why does my program continually corrupt an index?

I noticed a couple of people asking for help on this. Could you please tell me why my program might continually corrupt an index? I find that when I am going about entering information into the table, I exit the application and come back in I always get this error and don't know how to stop it from occuring. Am I missing a crutial step in properly closing the tables that could cause this?

Are you closing and freeing the table before you close? While implicit destruction of objects is perfectly legal, I've found that with respect to data access objects, you need to free them explicitly in the FormClose method. For instance:

Table1.Close; //Disconnect from the BDE
Table1.Free; //Free the resource
Data Access components have an annoying habit of leaving themselves in memory if you don't explicitly free them.

In your case, the result is that you actually may not have a corrupt index. But because another copy of the table is already in memory, your program sees this as a conflict.

DevX Pro
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date