Set single dbase password
- From: "A C" <no@xxxxx>
- Date: Tue, 4 Oct 2005 13:08:23 +1300
Hello
If we wanted to secure a database simply to stop 3rd parties from accessing
the database, but we dont want to set up different users with different
permissions or restrictions etc, is there any disadvantages with simply
using the Set Database Password option rather than creating mdw and user
groups and users etc?
Is it any less (more) secure? What are the up and downsides from doing
this?
Thx
AC
.
Relevant Pages
- Re: Security not clicking
... looked good until I copied the secured database to the network. ... Joan Wild wrote: ... When I rejoin the system mdw, ... split the database when it is secure or when it is not secure? ...
(microsoft.public.access.security) - Re: Word 2007 Missing User Level Securitty - ARRRGGGGHHHH What were they thinking?
... File servers aren't secure? ... Access predates Windows security, ... database system has never been updated or kept current. ... the OS-based database server product, ...
(microsoft.public.access.security) - Re: security wizard cannot be run
... You need to open your database using your secured mdw (i.e. the desktop ... Open Access (not via the shortcut). ... Create a new mdb and import everything from your 'secure' mdb. ... Once the database opens, the ...
(microsoft.public.access.security) - Re: security wizard cannot be run
... OK - I opened the database using the secure mdw using a username and password. ... I granted full permissions to the user group. ...
(microsoft.public.access.security) - Re: Security not clicking
... split the database when it is secure or when it is not secure? ... mdb, with the same name, but it'll have a bak extension. ... You can use Start, Search, Files and Folders, and locate all mdw ... unsecured database to continue enhancing security. ...
(microsoft.public.access.security) |
|
