[AccessD] Cascade-delete (was: Estimating Help)

Yes, I have been lucky. :) All the databases I've designed (with the
exception of my very first) I've locked the user's totally out of the
backend. They can only do what I give them security to do with the exception
of one power user that I've really (and I stress really!) trusted.

I supposed I'll be one of those that has to be burned before I follow the
path of wisdom. :) I definitely can see that situation you described
happening if you have a project where the client isn't willing to pay for
the administrative interface.


Jeanine Scott
Sr. Systems Analyst
Spindustry Systems
515-669-2074
jscott at spindustry.com

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
information. Any unauthorized review, use, disclosure, or distribution is
prohibited. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message including any
attachments.

-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com]On Behalf Of John W. Colby
Sent: Saturday, February 01, 2003 2:43 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Cascade-delete (was: Estimating Help)

Some of us are just luckier than others I guess.  Never had a user rip the
guts out of your database by trying to delete a client that they "weren't
doing business with" at the moment.

I should have such users!  ;-)

John W. Colby
Colby Consulting
www.ColbyConsulting.com