Hello Mark
 
Sometimes this error is caused by having a row with blanks or nulls in the table key fields and when an insertion occurs it also tries to insert blanks in the key fields.
 
Generally the error message relates to inserting an row which has the same primary key as an existing row. So look at the data using DBD32 and find a row which is the same as a row would be if the user inserted a new row.
 
Regards
 
Russell
----- Original Message -----
Sent: Tuesday, July 17, 2001 11:55 AM
Subject: [DUG]: Key Violation

Hi
 
I have a Paradox table with a composite primary key made up of:
DocketNo    Integer
DocketCheck Char(1)
DocInd    AutoIncr
 
I have also defined a secondary index on DocInd (EntryOrder), which is used whenever I want to order the table in the order of entry.
 
The client site has recently done some bulk deleting from this table and now cannot post to the table, getting error
"Key Violation: Index - EntryOrder"
 
I have tried deleting the index files and recreating them, but to no effect.
 
Can anyone throw any light on this or suggest any remedies.
 
Thanks
 
Mark 

Reply via email to