Rocky Smolin - Beach Access Software
bchacc at san.rr.com
Wed Jul 26 19:21:19 CDT 2006
But now you're talking about real deliberate mischief instead of just curiosity or error. Is this a problem in this environment? Rocky RANDALL R ANTHONY wrote: > Ah, that's right, it could still be linked via another db. > > >>>> "Mark A Matte" <markamatte at hotmail.com> 07/26/06 4:29 PM >>> >>>> > Hiding the tables does not prevent linking. > > I'm not sure I can even do this...but the solution I've been asked to > provide is a way for someone to view a report...not have access to the > > data...just view the report...this way no searching is allowed. I can > do > part of this by have a form at startup that turns off the bypass...gets > rid > of ALL menus and shortcuts...and opens the report...this however does > not > prevent them linking to the data from another db. > > Any ideas? > > Thanks, > > Mark > > P.S...as for the reason why...lets just say there is a reason there are > so > many lawyer jokes. > > > >> From: "RANDALL R ANTHONY" <RRANTHON at sentara.com> >> Reply-To: Access Developers discussion and problem >> solving<accessd at databaseadvisors.com> >> To: <accessd at databaseadvisors.com> >> Subject: Re: [AccessD] Secure a DB...kinda? >> Date: Wed, 26 Jul 2006 16:08:38 -0400 >> >> The quick and dirty might be to just hide the tables and disable the >> shortcut keys unhide function or the toolbar. >> >> >>>>> <DWUTKA at marlow.com> 07/26/06 4:04 PM >>> >>>>> >> 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 >> -- >> 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 >> > > > -- Rocky Smolin Beach Access Software 858-259-4334 www.e-z-mrp.com