Did I understand you correctly? Can you add deleted() to your index? Say I have two records that both have the same cust_id, but one record is deleted. Could I have cust_id has my primary index, with somehow including the deleted()?

Brenda

>After briefing through the intense list of responses, I didn't see any recommendations of recycling deleted records. This was a concept that I knew some people to use and has had an artical in the Foxpro Advisor.

>If you have an index on the deleted() status or on a flag field to identify that a record has been deleted, you could go by means of blanking out the misc fields (other than the candidate unique key). Then during an insert, before physically adding a new record, find the first record with the deleted() or flag field. If found, reuse that record and populate the fields as needed, otherwise add a new one.

>Again, I didn't see this buried anywhere in the responses since the initial inquiry.


>>Hate this "marked for deletion" crap. I come from an SQL environment that when you deleted a record, it was gone. If you wanted to mark records for deleteion, you added a delete flag column to your table. We never allow our clients to see deleted records, and they never have the opportunity to undelete. Yet they have to run a pack and reindex periodically.
>>
>>Is there a way to truly (madly, deeply) delete records from a table?
>>
>>Brenda