|
Why would you want to recover deleted records. Your system should always have an audit trail for anything that you delete, so you should be able to re-key where necessary! >>> -----Original Message----- >>> From: Roger Boucher [mailto:RBoucher@stanpac.com] >>> Sent: Thursday, August 26, 1999 5:23 PM >>> To: 'MIDRANGE-L@midrange.com' >>> Subject: Reuse deleted records (was SQL vs DDS) >>> >>> >>> This brings to mind a question... what if you want to >>> recover deleted >>> records. I am assuming that if you reuse deleted records >>> you wouldn't be >>> able to recover them using any of the utilities available >>> for that purpose? >>> >>> >>> -----Original Message----- >>> From: Jim Langston [mailto:jlangston@conexfreight.com] >>> Sent: Wednesday, August 25, 1999 1:23 PM >>> To: MIDRANGE-L@midrange.com >>> Subject: Re: SQL vs DDS >>> >>> >>> Actually, there is only one reason I have come up with to >>> reusedeleted *NO. >>> I asked that same question a few years ago, and the >>> consensus was it was >>> useful for debugging. >>> >>> Quite a number of times someone comes up and says they just >>> ran a job, they >>> did it totally wrong, could I fix it? I ask them for >>> invoice number, >>> container >>> numbers, no, they don't have the numbers. >>> >>> So, I just work with the file using PDM and do a 5 on the >>> member, jump down >>> to the bottom and I can see the last records that were added. >>> >>> If I had ReUseDeleted *YES I wouldn't know that the last >>> records were >>> actually >>> the last records added to the file. >>> >>> That is the only reason people have come up with when I >>> asked. As such, >>> some >>> files I have ReuseDeleted *YES and some I have it as *NO. >>> >>> Regards, >>> >>> Jim Langston >>> >>> John P Carr wrote: >>> >>> <SNIP> >>> >>> > (BTW, I don't know why anyone would not be >>> > using ReUseDeleted Records *YES). >>> >>> <ENDSNIP> >>> >>> >>> +--- >>> | This is the Midrange System Mailing List! >>> | To submit a new message, send your mail to >>> MIDRANGE-L@midrange.com. >>> | To subscribe to this list send email to >>> MIDRANGE-L-SUB@midrange.com. >>> | To unsubscribe from this list send email to >>> MIDRANGE-L-UNSUB@midrange.com. >>> | Questions should be directed to the list owner/operator: >>> david@midrange.com >>> +--- >>> +--- >>> | This is the Midrange System Mailing List! >>> | To submit a new message, send your mail to >>> MIDRANGE-L@midrange.com. >>> | To subscribe to this list send email to >>> MIDRANGE-L-SUB@midrange.com. >>> | To unsubscribe from this list send email to >>> MIDRANGE-L-UNSUB@midrange.com. >>> | Questions should be directed to the list owner/operator: >>> david@midrange.com >>> +--- >>> +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.