DE INDEXING A DATA BASE

  • Thread starter Thread starter PCOR
  • Start date Start date
P

PCOR

Hi
I have a database that consists of over 600 names, address ,phones etc

Two of these people have moved away and no longer should be in the data
base
How do I go about deleting these names from the data base with screwing
things up
I have heard that it can be DEINDEXED...whatever that means.
Or can I just remove the info from the NAME file?
Appreciate you help
Ian
 
Hi
I have a database that consists of over 600 names, address ,phones etc

Two of these people have moved away and no longer should be in the data
base
How do I go about deleting these names from the data base with screwing
things up
I have heard that it can be DEINDEXED...whatever that means.
Or can I just remove the info from the NAME file?
Appreciate you help
Ian
Click to expand...

Removing data from a table does NOT require removing indexes from a
database, and in fact removing indexes won't help!

Simply delete the records that you no longer want to exist. If you
have Relationships defined (say, from the Contacts table to the Phone
table) you can open the Relationships window; select each join line;
and check the "Cascade Deletes" checkbox. Now instead of giving you an
error message when you delete a Contact having a record in the Phone
table, it will delete both the contact and the phone record
(permanently and irrevokably - make a backup of your database first!)
 
It worked...Many thanks

John Vinson said:
Removing data from a table does NOT require removing indexes from a
database, and in fact removing indexes won't help!

Simply delete the records that you no longer want to exist. If you
have Relationships defined (say, from the Contacts table to the Phone
table) you can open the Relationships window; select each join line;
and check the "Cascade Deletes" checkbox. Now instead of giving you an
error message when you delete a Contact having a record in the Phone
table, it will delete both the contact and the phone record
(permanently and irrevokably - make a backup of your database first!)
Click to expand...
 
Back
Top