Hi Mark,
Hard to say, but I guess the first place to look would be the autoinc
field. Though I use these as the single primary key in C/S databases,
I've generally avoided them in Paradox tables. No compelling reason,
just that they cause a lot of stress when things go bad. In your case,
you could perhaps have used a DateTime stamp etc, which would have also
been informative to the users.
How were the "bulk deletes" done? Was there a problem there?
Can you view the table ok? Any autoinc fields look screwy?
Does Restructuring help? Perhaps after deleting the index (.PX?)
Can you work out what the next autoinc number is, and confirm whether or
not the next insert is going to bomb? This may point to an existing
record which you may be able to toss.
Sorry I can't be of more help.
Craig.
Mark Howard wrote:
> Hi I have a Paradox table with a composite primary key made up
> of:DocketNo IntegerDocketCheck 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
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED]
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
