John W. Colby
jwcolby at colbyconsulting.com
Mon Nov 1 17:29:04 CST 2004
One thing you should do is set up relationships with child tables, then turn cascade delete off. This will prevent this in some instances. John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Eget Sent: Friday, October 29, 2004 10:54 AM To: AccessD at databaseadvisors.com Subject: [AccessD] access security I am trying to fix a security issue at my site. My managers like to edit or delete records that they think are inappropriate in a product audit database and usually fail to inform anyone of this. I have locked them out of the backend access by the front end with the directory properties of windows for the back end. But this also does not allow them to enter records either. But I would also like to take one step further and not allow individuals that are entering records into the database from either deleting or editing other individual records. Can anyone share with me how they may have done this in the past? Thanks in advance John -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com