How to avoid '' Key Violation ' error ?

[benkiliane]

My Table is created and it has primary key composed by three fields. I want to save record in the primary key Fields even it's already exists.
For the primary key I put UNIQUE = false but I have always key violation.
Can you Help me please as soon as possible.
Thank you

 

[mikeEd]

You can't. That's the point of Primary Keys; they must be unique. Presumably you want to restrict the PK to only 2 of those 3 fields.

 

[delphiman]

When you create your table make one of them a N field, make it an Auto-increment field and Index on that. That way every time you create a new record it is unique and you cannot get a key-violation.

Hope it helps.

 

[LucieLastic]

Put indexes on the foreign key fields, and don't make them Primary keys.

You say you want to save a record even if it already exists, if the records are exactly the same why are you saving it and if not what is the difference with the 'same' records ?

lou

 

[LucieLastic]

Sorry, ignore my question about the records being exactly the same (can't read properly when early in morning), you mean when the key fields are the same.

 

[svanels]

I would be cautious on using autoincrement fields. Borland itself doesn't use them. If you look at the MastApp demo you will see a nice work around for creating unique key field numbers S. van Els
SAvanEls@cq-link.sr