[AccessD] Missing records

Honestly, I'm not sold on Cascade Delete being off.  It makes it much easier
to work if it's on when record does require deletion (like your invoice
example).

I really prefer to control it at the form by not allowing deletes there.  If
they can't delete it at the form level then Cascade Deletes never becomes an
issue.

Reuben Cummings
GFC, LLC
812.523.1017


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Gustav Brock
> Sent: Friday, February 03, 2006 11:08 AM
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Missing records
>
>
> Hi Reuben
>
> Well, you didn't do your homework ...
>
> But as you note, it is very easy to correct: Enforce Referential
> Integrity and turn OFF Cascade Delete between Employee and
> Employee Journals (or whatever the details are).
> This way you don't need to do anything else. If a journal exists,
> the Employee of that can not be deleted no matter what the user
> do - not even if he/she has table level access. Very powerful.
>
> /gustav
>
> >>> reuben at gfconsultants.com 03-02-2006 16:47:40 >>>
> I think John nailed it.  Check all relations to this table.
>
> Just yesterday I had to restore about 14,000 expense records
> because she had
> deleted an employee rather than "terminating" (which means enter the date
> the employee was terminated) that employee.
>
> Cascade Delete is very powerful, which makes it very scary.
>
> I now have two things to change in my app - a relation property and to not
> allow deletes of employees.
>
> Reuben Cummings
> GFC, LLC
> 812.523.1017
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>