Re: Different Users for Access 2000

From: Tim (tim_gould_at_ryder.com)
Date: 07/30/04 

Date: 30 Jul 2004 10:06:46 -0700

The shortcut refers to three files:

The mdb file is, well, the database, but it is now aware that it needs
a password and user login before it can open.

The user details are stored in the mdw file (the WorkGroup). When you
type in your login, it is compared with this file to see if you are
allowed access.

Finally, you need good old MSACCESS.EXE to run the thing at all.

The shortcut basically opens Access and passes it the locations of the
database to open and the WorkGroup file. Access takes over from there.

You should move your mdw file to the server. You don't need to
recreate it. So long as you open Access from a shortcut which points
to it, you will still be able to edit the WorkGroup and add/delete
users. But every user will need to use the same WorkGroup file, so it
needs to be somewhere where they can all access it. Typically this
would be the same folder as the database itself.

You should end up with:
One mdw (workgroup) file on the server
One mdb (database) file on the server
Each user has MS Access installed locally on their own PC.
Each user has a shortcut that points to these three files. The
shortcuts are likely to be different because the location of
MSACCESS.EXE may vary from machine to machine. Also, different users
may use different letters for the server drive.

That answers you immediate question. The next bit (below) is looking
forwad a bit further, so don't worry about it until you've got the
shortcuts etc working.

Your next task is to Split the database, which means splitting it into
two separate files. One contains all the data (tables) and stays on
the server. This is the "Back-End Database". The other part contains
all the forms, queries, reports and modules and you can give each user
a copy to save on their own PC. This is the "Front-End". There is a
Splitting Wizard in Access to do this.
The shortcut would then point to the Front-End on the users PC instead
of the database on the server. The Front-End knows where the tables
are and everything works pretty much exactly the same (certainly as
far as the Users are concerned there is no difference), but now you
aren't squabbling over who can use the database; you all can - at the
same time.

"Kelvin" <yew mhis@intr.mhi.co.jp> wrote in message news:<6df501c475d2$d2f17d00$a301280a@phx.gbl>...
> The database that I am going to create is going to be
> stored in the main server eventually and all 6 users,
> including me will be connected to the main server.
>
> Will the link that I have created earlier still works?
>
> "C:\Program Files\Microsoft
> Office\Office\MSACCESS.EXE" "C:\Kelvin's doc\Access
> Testing\db1.mdb" /wrkgrp "C:\Kelvin's doc\Access
> Testing\SECURITY.mdw"
>
> Or
> Must I re-create the workgroup (.mdw) in the server itself
> and perform the steps again on the database stored in the
> server?
>
> Or
> Work on my desktop first, like what I currently did. When
> the database is stored to the server, I just need to
> change the "path to mdb"?

Relevant Pages

  • Re: i give up...please tell me how to remove security
    ... Access Security: www.ltcomputerdesigns.com/Security.htm ... > When I copied the database over I also copied the "secured.mdw" file and ... > shortcut that I used to open it. ... I changed the workgroup in the target of the shortcut to refer to this ...
    (microsoft.public.access.security)
  • Re: Access 2000
    ... I have created and then logged in under the workgroup WRKGRP on my system, ... copied their secured.mdw file to my system, and given my shortcut the same ... > The database is probably secured. ... "You do not have the necessary permissions to ...
    (microsoft.public.access.security)
  • Re: Using Workgroup Accounts on a Network
    ... I split the database, but when I split it, I cannot access the BE ... tables to the BE on the server? ... to use the "Join a workgroup," So, how do I get the permissions and workgroup ... you do not normally select the right workgroup file by "joining" ...
    (microsoft.public.access.security)
  • Re: User and Workgroup was screwed
    ... We have a Access database for logging all the activities we do everyday. ... If you use a shortcut, right-click the shortcut and examine the Target property; ... Make sure the .mdw file is in the path specified. ... If you don't use a shortcut to open your db, then the machine was probably "joined" to a workgroup. ...
    (microsoft.public.access.security)
  • Re: Neophyte question about workgroups
    ... This workgroup file is placed on your local drive at ... >> shortcut method as I cant think of it off the top of my head. ... >> read if you start securing Access database. ... >> Immanuel Sibero ...
    (microsoft.public.access.security)