>>I wanted the primary index to ignore deleted records using SET DELETE ON,but when i delete one and add another with the same primary key,
>>the "Duplicate primary key error" appears.
>>
>>I solved this problem creating a filtered index (FOR NOT DELETE()),
>>but Rushmore Technology won't use filtered indexes, so i think
>>the application will lose performance when tables have many records.
>>Am i right?
>>
>>Is there any other solution?
>>
>>I can't execute a PACK statement from the application because the
>>multiuser environment won't have exclusive access on the table.
>>
>>
>>Thanks
>>
>>Juan Carlos
>
>I get around this by not reusing primary key values.

Interesting. What method do you use to generate unique values? Do you use an
different table that holds the next key value or do you find the max value in the table
and increment? Or is there another technique?

- Chris Holtz