>>>>>Hello,
>>>>>
>>>>>I worked on a table which has a primary index called "Key". This table is included in the DataEnvironment of one of my form, with Private DataSession. Problem occur when I tried to add (by APPENDing) a new record with a value which had been deleted previously. The message I got is "Uniqueness of Index KEY is violated." By PACKing the table after DELETEing a record would solve the problem. Is there any other way (other than RECALLing) which I could use back the same KEY value without having to pack the table? 'Cos I don't want to open the table as EXCLUSIVE.
>>>>>
>>>>>Thanks,
>>>>>juan
>>>>
>>>>You touched the reason why primary key should be surrogate, e.g. sequential number, which will never be repeated.
>>>You can define your primary index to "fieldname for not deleted()". There's been a bit of discussion on this subject, but I think that it is a valid alternative.
>>
>>This is not healthy alternative, primarily because index tags with FOR filter cannot be used for Ruhshmore purposes.
>True enough. I also have the primary field indexed without a fliter clause.

Yes, but it will not be 'primary' key anymore and you cannot use it for RI triggers or for View key fields etc.