[AccessD] 2 Questions

Yes I know Gustav, but I was writing an email not a tutorial.

BUT it is  more dangerous, because it can be forgotten about for ages and
ages and then suddenly! There it is in your face...no thanks.  For
you,maybe. For me, no way.

Max


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
Sent: Wednesday, March 10, 2010 2:33 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] 2 Questions

Hi Max

It is not "some" switch. There is one specific switch that controls
cascade-deletes for a relation. 

If anyone is unsure how to operate this or to handle referential integrity
in general, I will certainly recommend to read it up at the soonest as this
is the heart and soul of a relational database.

As for how "dangerous" cascade-deletes are, it is not different from any
other action that alters or deletes data in the database.

/gustav


>>> max.wanadoo at gmail.com 10-03-2010 15:05 >>>
Tony,

You are being mislead here. Nobody is saying that Referencial Integrity
should not be practised. All I am saying is that I do not use the built in
tools in Accesss to do it.  I do it manually.  Ignore the band wagon which
has sprung up by those who didnt read it correctly (and if that statement
doesn't get a response then I do not know what will !!).

The reason I do not use it is because I got badly bitten by Cascading
Deletes some years ago. I now control what gets deleted and under what
circumstances and not leave it to some "switch" being turned on in Access.

So, use Ref Int but you choose how to implment it.

Max



On 10 March 2010 13:34, jwcolby <jwcolby at colbyconsulting.com> wrote:

> Tony,
>
> Referential integrity is the foundation of a database.  Without it you are
hopelessly lost.



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