DWUTKA at marlow.com
DWUTKA at marlow.com
Wed Jul 26 15:04:00 CDT 2006
Hmmm, a little tough to do that. Access User Level security can lock users out of objects, including tables, however, that means they can't get to them at all. I believe if a user has read rights, they still can't 'link' the table, not absolutely sure about that, have to check. But if they can read the data from the table in a form, they will be able to open the table in the database window. If reading doesn't allowing linking, you could always hide the DB window (or hide the access window). That would prevent the user from getting to the tables directly in the database. Even if read-only permissions don't allow a user to link, it still wouldn't be perfect, you'd be able to view the data with ADO/DAO code still.... Just curious, what's the actual goal here? Drew -----Original Message----- From: Mark A Matte [mailto:markamatte at hotmail.com] Sent: Wednesday, July 26, 2006 2:34 PM To: accessd at databaseadvisors.com Subject: [AccessD] Secure a DB...kinda? Hello All, I would like to do 'something' with access...I want to be able to send out an MDB or MDE...and no matter who opens it...no password required...but if someone were to try and link or get to the tables...a password would be required? I could do this with a FE/BE scenario...but this is not an option. Any ideas? Thanks, Mark A. Matte -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com