[AccessD] Another challenge I need help with

[James Button]

Re undeleting priceless -

Definitely !

I'd add having the id of the person specifying the entry deletion and time that they did it is also an essential. 
And so much easier to note that on the data records as they get set to inactivate.

JimB


-----Original Message-----
From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of John Colby
Sent: Tuesday, November 6, 2018 4:36 PM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>; John Bartow <jbartow at winhaven.net>
Subject: Re: [AccessD] Another challenge I need help with

I designed and used a framework for my forms.  All deletes in all tables 
(forms) marked records inactive, and re-queried the forms to only show 
active records.  Managers were tasked with deleting inactive records if 
they so desired.  Very few ever did.

It was a bit more work of course with reports always filtering out 
inactive records.  But to be able to "un-delete" records was priceless.


On 11/5/2018 3:02 PM, John Bartow wrote:
> I have at least one application where the delete marks the account as inactive rather than actually deleting the record. All displays then filter for active. There's an administrator level function to review inactive accounts with the ability to actually delete the record.
>
> -----Original Message-----
> From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of Stuart McLachlan
> Sent: Sunday, November 04, 2018 1:54 PM
> To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Another challenge I need help with
>
> Yes, I often do that.
>
> I also sometimes use a second message that prompts "Are you real sure that you want to delete this record".
>
> In one application I actually had a third one:
> "LAST CHANCE - ARE you REALLY SURE you want to delete this record!"  :)
>
>
> On 4 Nov 2018 at 15:12, Joe O'Connell wrote:
>
>> Maybe it is just my users, but they sometimes need to be protected
>> from themselves from automatically hitting the enter key whenever a
>> msgbox is displayed instead of reading the message.  Instead of just
>> acYesNo, I add an option to default to No and to display a question
>> mark so  the buttons become vbYesNo+vbDefaultButton2+vbQuestion
>>
>> Joe O'Connell
>>

-- 
John W. Colby

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