|
One more, although it has limitations depending on the implementation: UNDO. For updates, keep a temporary file of the changes and allow them to be undone (you can already "undo" adds and deletes - it's the updates that can't currently be undone). The problem with this approach is that mass changes using SQL wouldn't be undo-able. -or- Have a "wizard" that creates a journal and turns on journaling prior to a session. The downside to this is that removing journaling from a production file is difficult. Joe > -----Original Message----- > > I planning to start another round of enhancements to WRKDBF shortly. (I > know - it's been awhile!) Does anyone have any specific requests they'd > like me to consider?
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.
midrange.com
