[AccessD] Secure a DB...kinda?

Charlotte Foust cfoust at infostatsystems.com
Thu Jul 27 10:20:05 CDT 2006


It automates passing in the password for Access security, not a database
password or code password.  We build shortcuts for our users that open
the application to the correct settings without their having to deal
with a login dialog.  If they open the database from Access without the
password, they get dumped out or the face a login dialog, depending on
which workgroup they point at.


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
Sent: Thursday, July 27, 2006 7:57 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Secure a DB...kinda?

ok...all the help files and articles imply that I can use the following
in this setting:  /pwd<password>

My question is what does /pwd <password> in the Command-Line Arguments
setting on the ADVANCED tab of OPTIONS do?

Thanks,

Mark


>From: "Charlotte Foust" <cfoust at infostatsystems.com>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "Access Developers discussion and problem 
>solving"<accessd at databaseadvisors.com>
>Subject: Re: [AccessD] Secure a DB...kinda?
>Date: Thu, 27 Jul 2006 07:42:36 -0700
>
>It's there to hard code a value you can return with the Command() 
>function.  If you pass in a command line argument using /cmd, you can 
>also read that with the Command() function.  The value returned is a
>variant, not a string.   If you pass it in from a command line, it has
>to be the last option on the command line.
>
>
>Charlotte Foust
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
>Sent: Thursday, July 27, 2006 7:23 AM
>To: accessd at databaseadvisors.com
>Subject: Re: [AccessD] Secure a DB...kinda?
>
>Its just what the lawyer was asking for...I gave them a tool to view a 
>large number of records...he wanted to share the info with other 
>lawyers...but did not want them to have the functionality he had.  His 
>request was 'No searching' and 'No exporting'...just reading.  And it 
>had to be provided in a single file...No FE/BE...no install.
>
>I wasn't sure anything like this was possible...so thought I'd ask.
>
>Anyone know what the "Command-Line Arguments" setting is for on the 
>ADVANCED tab of OPTIONS?
>
>Thanks,
>
>Mark A. Matte
>
>
> >From: Rocky Smolin - Beach Access Software <bchacc at san.rr.com>
> >Reply-To: Access Developers discussion and problem 
> >solving<accessd at databaseadvisors.com>
> >To: Access Developers discussion and problem 
> >solving<accessd at databaseadvisors.com>
> >Subject: Re: [AccessD] Secure a DB...kinda?
> >Date: Wed, 26 Jul 2006 17:21:19 -0700
> >
> >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
> >
> >--
> >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


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list