>Fred,
>
>>That's pretty much what I mean. A record that was just DELETEd would not be available for automatic re-use, via INSERT or APPEND. It could still be RECALLed as needed. If you did DELETE RECYCLE then yes, INSERT/APPEND could re-use it.
>>
>>We use a mechanism for SOME tables that records can be re-used if they are DELETEd and other tables that can be RECALLed. The main difference is the type of record, such as a customer record that was deleted could be recalled, but a list of items on an order could be recycled.
>>
>>PACK would not need to distinguish between the two types, it would still remove all records marked for delete.
>
>My original proposal was to set some tableproperties with DBSETPROP. See thread #277206. In this way you could set the desired behaviour per table.
>
>Walter,

I think I like your per table proposal via DBSETPROP(), but that's what I meant by DELETE RECYCLE. I find SET DELETED ON/OFF a bother, and potentially dangerous as well, especially since you're never really sure what the setting is at various places in the code. I was suggesting it to be implemented on the DELETE command rather than as a new clause of SET DELETE. If the DELETE command implemented it, you could then override the DBSETPROP() setting as needed on a temporary basis, but the DBSETPROP() could control that table's default recycling status if just DELETE or DELETE FOR was used.