[AccessD] Coding for backing up deletes

Yes, this isalmost exactly what I had in mind originally, though it has to
be said that SusanH's idea of adding a field has a lot in its favour. 

I'd be very keen to see the code that manages this delayed deletion route
for you, if possible. 

It seems to me to be something that everyone needs who has Users not under
the direct control. All the best
paul

-----Original Message-----
From: ranthony at wrsystems.com [mailto:ranthony at wrsystems.com]
Sent: Tuesday, August 03, 2004 5:00 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Coding for backing up deletes


Sorry to come in late on this one, but I've got an app that works in a very
similar manner.  The user can check a record as "completed" using a date
field and a checkbox.  A report can then be run showing "completed" items
ready for deletion.  A one-at-a-time or batch deletion can be run, which
removes those records from the main table to an "archive" table, which if
the need arises, can be used to restore the records to the main table.  It
also provides for reports to be run on the archived table for historical
program reviews, etc.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] 
Sent: Tuesday, August 03, 2004 10:43 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Coding for backing up deletes

Yes, that's a good and simple idea, Susan H, thanks very much.

-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net]
Sent: Tuesday, August 03, 2004 2:54 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Coding for backing up deletes


Do you really have to move it to another table? You could just add a field
-- Active/Inactive -- something like that. You'll have to remember to update
all your queries, etc., but unless there's some reason to really need to
move it to another table, I don't think I'd bother. 

Susan H. 

Any of our craftsfolk ever coded for something like this please?

The user wants to delete a file in a table. She goes to a form, and finds
the record. She clicks a button and the record is 'deleted' - only really it
goes into a waiting backup table ... just in case. 

Expert guidance would be appreciated.


-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com