[AccessD] Preventing childless parent records

...evil genius at work! :))))))

William

----- Original Message ----- 
From: "Dan Waters" <dwaters at usinternet.com>
To: "'Access Developers discussion and problem solving'" 
<accessd at databaseadvisors.com>
Sent: Monday, March 06, 2006 7:08 PM
Subject: Re: [AccessD] Preventing childless parent records


> Hi Don,
>
> I would add that prior to deleting those records, you should send an email
> to each person whose record is being deleted, along with enough 
> information
> from the parent record for them to re-create the parent and child records.
>
> A good time to go through this sequence is whenever the first person is
> logging on in the morning.
>
> You'll need to record the name of each person entering a parent record, 
> but
> that's probably already there, and you'll need another table to look up
> everyone's email address.
>
> I bet people will start paying more attention if they know that the 
> computer
> telling them they screwed up will NOT go away when they smile vacantly at
> the monitor!  ;-)
>
> Best of Luck!
>
> Dan
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Hadyn Morgan
> Sent: Monday, March 06, 2006 5:28 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Preventing childless parent records
>
> Hi Don
>
> You could always run a query on the closing of the form that deletes the
> records without children.
>
> Kind regards
> Hadyn
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Mcgillivray, Don
> [IT]
> Sent: Tuesday, 7 March 2006 11:42
> To: AccessD
> Subject: [AccessD] Preventing childless parent records
>
>
> Hello, All
>
> I have a data entry form for entering transactions where the main form
> holds the transaction header and a subform holds the header's details.
> Works as advertised, except that I have a user who has a habit of
> creating headers without adding line items.  She sets up the header,
> tabs into the line item section, gets distracted (I guess), returns to
> the form (after dealing with the distraction) and starts over for some
> reason.  Now, by virtue of having tabbed into the line item section, the
> header was saved, but because no line items were ever entered, the
> header is an orphan, or, more accurately, a childless parent.  Every
> week, I scan the data and find several of these records that need to be
> removed.
>
> My first approach was to educate the user about how to do data entry.
> My second approach was to educate the user about how NOT to do data
> entry.
>
> Both approaches netted me that vacant nodding smile that says "I don't
> know what you're talking about, but if I keep nodding like this, maybe
> you'll go away and leave me alone."  I'm sure you're all familiar with
> that look.
>
> This must be a common problem - the childless parent record, not the
> vacant nodding smile - but I'm struggling with how to detect the
> condition and disallow it.  Can anybody point me in the right direction?
>
> Thanks!
>
> Don
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.2.0/275 - Release Date: 6/03/2006
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.2.0/275 - Release Date: 6/03/2006
>
> -- 
> 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
>