SP1KEMAG00
SP1KEMAG00 at aol.com
Mon Nov 17 14:54:17 CST 2003
I've disabled the shift-key completely on a couple of my more recents dbs and either used a separate admin file to lock/unlock the file and/or built in some sort of backdoor (typically only available to my logon id). This has been more out of interest than to stop noisy users though - I'm not sure there's any that even know about the shift-key let alone anything with any tighter security! Shaun -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of StaRKeY Sent: 16 November 2003 20:01 To: Access Developers discussion and problem solving Subject: RE: [AccessD] A2K: Allowbypasskey 4th parameter Well actually I haven't been reading for a long time. After you mentioned this doc I started reading it but there's nothing I didn't already know. Usually I don't make use of the workgroup file because I find a user-defined security more flexible and easier to maintain. Code protection is not the issue for me and on the other hand I do not really want to use the 'owner permission' stuff. The shift-key feature is enough in combination with an mde though it would be nicer to have it locked tight. I guess this is where VB steps in;-) Thanks, Eric Starkenburg -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Robert Gracie Sent: zondag 16 november 2003 01:02 To: Access Developers discussion and problem solving Subject: RE: [AccessD] A2K: Allowbypasskey 4th parameter Eric, Ah yes, I see now... Nope your out of luck... but I guess you know that the db is not really going to be secure... You have read the "SECFAQ97" White papers correct? Robert Gracie www.servicexp.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of StaRKeY Sent: Saturday, November 15, 2003 4:36 PM To: Access Developers discussion and problem solving Subject: RE: [AccessD] A2K: Allowbypasskey 4th parameter Thank you for the reply Robert. Robert, I won't be able to prevend them these rights in their own newly created empty database. So my guess is that the 4th parameter is nice but not sufficient since from within this new empty database one would be able to change the property of the 'secured' database or am I missing something? Regards, Eric -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Robert Gracie Sent: zaterdag 15 november 2003 21:55 To: Access Developers discussion and problem solving Subject: RE: [AccessD] A2K: Allowbypasskey 4th parameter Yes, In order to keep them from changing the property you will need to revoke admin rights from every user and group in your db. Robert Gracie www.servicexp.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of StaRKeY Sent: Saturday, November 15, 2003 3:37 PM To: AccessD at databaseadvisors. com Subject: [AccessD] A2K: Allowbypasskey 4th parameter Hi All, I have a question about the 'allowbypasskey' property and in specific the 4th parameter when creating it (DDL). It is mentioned that having set this parameter to 'True' only admins are able to change the 'Allowbypasskey' property. Ofcourse this is nice to know but my question is: if one uses an empty Access DB with the default system.mdw and thus being an admin wouldn't it be possible to change the property from within this new database? TIA, Eric Starkenburg --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 14-11-2003 Tested on: 15-11-2003 21:37:27 avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 14-11-2003 Tested on: 15-11-2003 22:35:54 avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 14-11-2003 Tested on: 16-11-2003 21:01:27 avast! is copyright (c) 2000-2003 ALWIL Software. http://www.avast.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com