[AccessD] Missing records

> >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.

Not true.  Cascade Delete could still be used.  It would simply require a
different method of initiating the deletion of the parent record.  For
example, I may not allow deletes on the form.  However, I could allow the
user to select that record for deletion in some other manner and delete it
thru a function.

I understand the potential consequences of both methods and don't really
care who uses what method.  I think everyone here is smart enough to
determine which way is best for them in any particular app.  I happened to
overlook a property in one form and a ladt deleted 14,000 records.  I
recovered those records and have since corrected the form.

Everyone makes mistakes.  Fortunately, as humans we have an amazing ability
to quickly learn from those mistakes.

Reuben Cummings
GFC, LLC
812.523.1017


> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John Colby
> Sent: Friday, February 03, 2006 1:55 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Missing records
>
>
> >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.
>
> And so I design a new form and forget to.... I am a VP and
> remoting in from
> home and build a query and...  I am the power user and manage to
> get to the
> database window and...
>
> Your job is to outsmart the idiots.  God's job is to design better idiots.
> Who has been on the job longer?
>
> The database engine has these things for a reason.  You can't delete my
> client record I don't care WHAT you do, without deleting all child records
> first, in all child tables.
>
> Again, I don't care if you use them, I just care that you UNDERSTAND the
> consequences of using them.  Lord knows if you don't have time to build a
> delete query and a button that only supervisors can get to, you don't have
> time to design an Active / trash system.
>
> Whatever you do, do NOT believe that backups can always rescue your young
> *ss.  If some particularly smart idiot has been unknowingly
> deleting things
> over the last year, you will NEVER get all the records out of all
> the backup
> tapes.
>
> Understand the consequences, then make an informed decision.
>
> John W. Colby
> www.ColbyConsulting.com
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Reuben Cummings
> Sent: Friday, February 03, 2006 12:15 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [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
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>