Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Security / August 2004

Tip: Looking for answers? Try searching our database.

Creating a workgroup, Secure database, join a workgroup????

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Norman Fritag - 12 Aug 2004 11:44 GMT
Hi there

I have manage to create on my machine a work group and thought that I
secured this database.
I was quite happy until I tested it, accessing the "secured database" on the
network from another machine and look what happened: I was able to open the
database without any effort!! Not prompt no nothing, strait access!!

What am I missing here?

I am using a shortcut string to initiate accessing the secured database. The
Database is although not joint with the system.mdw, but with mysytem.mdw,
which causes that if I want to open any other database, which I thought are
not joint with the mysystem.mdw are requiring all of its sudden passwords
too!!!

Does this method mean that what I have done on my machine only applies to my
machines mysystem.mdw and anyone else uses their system.mdw??

What am I missing here??
What else is required to secure this database??

any hints are much appreciated.

Kind regards

Norman F
Joan Wild - 12 Aug 2004 15:28 GMT
> Hi there
>
[quoted text clipped - 6 lines]
>
> What am I missing here?

You missed a step in securing it.  Either the Admin user still owns the
database, or the Users Group has permission to objects.

> I am using a shortcut string to initiate accessing the secured
> database. The Database is although not joint with the system.mdw, but
> with mysytem.mdw, which causes that if I want to open any other
> database, which I thought are not joint with the mysystem.mdw are
> requiring all of its sudden passwords too!!!

Databases are not joined to a workgroup file.  The workgroup used is session
based.  Every time you start Access it uses a workgroup file - even for
unsecured databases.  It uses whatever workgroup you are currently joined to
by default.  Out of the box, it silently logs you in as Admin using the
system.mdw workgroup.  That is why, since you are joined to mysystem.mdw,
you are getting a login prompt for every database.

Leave your computer joined to system.mdw and use desktop shortcuts to start
your secure databases.  The shortcut can include the /wrkgrp switch which
will override the default mdw for just that session of Access.

Follow the steps in
Security FAQ
http://support.microsoft.com/?id=207793

I've also outlined the steps at www.jmwild.com/AccessSecurity.htm

Signature

Joan Wild
Microsoft Access MVP

Norman Fritag - 12 Aug 2004 21:40 GMT
Joan,

thank you!

Regards Norman
> > Hi there
> >
[quoted text clipped - 32 lines]
>
> I've also outlined the steps at www.jmwild.com/AccessSecurity.htm
Denny - 19 Aug 2004 05:01 GMT
Hi all,

I am stil not clear how to achieve this.
It's true that you can make your database secure through shortcut.
But other user on the network can always access the database straight
to the .mdb file.
In this case they will use their own "default" workgroup file and
still able to make changes.

Am I missing something here?

Many Thanks.

Regards,

Denny
Joan Wild - 19 Aug 2004 13:47 GMT
> Hi all,
>
[quoted text clipped - 6 lines]
>
> Am I missing something here?

Yes.  If they can even open your database using their own default workgroup
file, then you missed a step in securing it.

Check that the users group has no permissions to anything (check the
database object).  Check that the Admin user doesn't own any objects.  Those
are the two most common reasons.

If you implement security, following *every* step, your users will not be
able to open the mdb without using the correct mdw file.

Signature

Joan Wild
Microsoft Access MVP

Denny - 25 Aug 2004 03:07 GMT
Thanks Joan,

I've redone the steps and made it works!!
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.