Losing Table Index

  • Thread starter Thread starter David
  • Start date Start date
D

David

I have a secondary table that contain various fields that hold the indexes
of other table records. This secondary table is independent of the primary
table that contains the records.

Question:
1) When I repair or compact the DB, do table indexes change?

2) Is there anyway to save the indexes of the primary tables in a secondary
table field and maintain the link to the primary table such that if the
primary table record index changes (e.g. repair or compaction) the secondary
table fields (which hold the index values) also change?

Thanks
David
 
John thanks for the response:

I have what I call a "Restore table" (secondary table). When I shutdown the
App, I save selected "primary table" record id's (e.g. autonumber) into the
Restore table. Then when I restart the App, I use the Restore table as a
quick loader for my arrays which may contain all --or some -- of each
"primary table" records.

For some reason "very infrequently" I have a corruption during load. My
error logs directs to this load procedure (error log doesn't id specific
line).--but-- wasn't sure whether compacting or repairing the DB results in
changing table record id's (e.g. autonumber) especially where a hole exists
in the numbering (i.e. record was deleted).

David
 
wasn't sure whether compacting or repairing the DB results in
changing table record id's (e.g. autonumber)
Click to expand...

It does not. Compaction will NOT change any stored values in any table.
especially where a hole exists
in the numbering (i.e. record was deleted).
Click to expand...

Autonumbers will always have gaps, and these gaps are not affected by
compaction.
 
Back
Top