[AccessD] Missing records

John; Excellent points... programming is not supposed to be easy, on the
Programmer but easy on the Client. I handle service agreement as if they
were insurance policies.

Just as mountain climbing may void your life insurance so may not doing
backups void your service agreement or at least cost you more. 

It is pointless for the insurer to wreak their own policy but writing bad
code which the client should not be expected to pay for... like leaving the
cascading delete on and praying nothing happens.

Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: February 3, 2006 2:08 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Missing records

That is a good point.  How critical is the data?  If it is accounting data
for a vets office, then you better treat it differently than if it is a
recipe database for your wife.

The bottom line is that controlling deletes at the form level simply isn't
very secure at all.  As a professional I can get around that at will.  I
(some programmer) might very well be HIRED INTENTIONALLY to build a
completely different application or FE that talks to your tables.  The fact
that you prevent these deletes in YOUR app doesn't mean I am preventing them
in mine!  Even a non professional can often "find" a way", usually
accidentally.  I have never seen anyone find a way around JET (or SQL
Server) when cascade deletes were turned off, other than deleting the
records from child table up, intentionally and with forethought and malice.


I gave up on preventing hackers from doing their damage.  I am very
successful preventing accidental damage, and my success comes from using the
tools that Jet (or the database engine) gives me, free of charge.  My (the
programmer's) convenience should not be the issue here.

John W. Colby
www.ColbyConsulting.com 


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Friday, February 03, 2006 3:30 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Missing records

Hi Rueben:

It is so system dependant on the way records are handled. When it comes to
POS and Accounting systems, records can simply not be removed as there would
be no way to follow the course of transactions or perform a forensic audit.
If Access had a cascading record de-activation as well as a delete that
would save a lot of coding.

My two cents worth.
Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Reuben Cummings
Sent: February 3, 2006 9:15 AM
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