Re: Security on a common server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

hackmn_g wrote:
>
> The Questions: Being that this database is sitting on a common server
> for the users to access, how can I secure the database? I am sure
> that the lack of a logon prompt from another computer has to do with
> the workgroup information file sitting on my local machine.

More than that, it has to do with security not being set up correctly. You
must follow the steps exactly, not missing anything. You don't mention
version, so I can't comment on whether the wizard has done the job for you.

On the other computer, they shouldn't even be able to open your secure mdb
without using the correct mdw file.


> Can I
> simply copy the system.mdw file onto the server?

The question suggests a possible further problem. Did you use system.mdw or
did you create a new workgroup to secure the mdb? If the former, then you
missed the very first step in securing it. Once you have security setup
correctly (and a good test is to see if you can open it from another
computer), then yes put the secure mdw file on the server.

> If so, will I then
> need to join each individual's machine to refer to this workgroup
> information file sitting on the common server? Is there an easy way
> of doing this? Can a user's machine refer to more than one workgroup
> information file, in case he/she has a local database?

The preferred method is to leave them joined to the standard system.mdw
workgroup file. Give them a shortcut for the secure mdb and in the target
point to the correct secure mdw to use for just that session. All other
sessions will use the system.mdw. The target would look like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

A final note: you really shouldn't have multiple users accessing the single
mdb on the server. You should split the database (see
http://www.jmwild.com/SplitSecure.htm for how to split a secure mdb). Put
the backend on the server and give each user a copy of the frontend on their
PC. The frontend will contain links to the tables in the backend. Their
shortcut would then be modified so that 'path to mdb' is the path to the
frontend.

--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • 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: Created on Access 2003, but.......................
    ... But that's not secure under any scenario, as any port scanner ... Well, you still need a userid, password and database name. ... You're assuming the server remains in a secured configuration. ...
    (comp.databases.ms-access)
  • Re: Access and ASP.NET working together - any advice?
    ... Access is not secure at all, ... however if you have Access on a secure PC that is running a web server ... the Access database will be less vulnerable than SQL Server 2000 database ... is there any problem using Access to do all our internal work while ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Use Level Security Shortcut
    ... You'd put the backend on your server, and give each user a copy of the frontend on their computer. ... Change the paths to reflect the location of the frontend on your PC, and the path to the secure mdw, which you put on the server. ... an actual shortcut to the mdw was setup by the wizard on my desktop. ... desktop which is the only way the database can be opened. ...
    (microsoft.public.access.security)
  • Re: Distributing a database on a network
    ... Currently the users can access the database without a password. ... mdw file. ... > Put the mdw that you secured it with on the server. ... > shortcut to launch the secure mdb. ...
    (microsoft.public.access.security)