Re: Netowrk use can't open database

Tech-Archive recommends: Speed Up your PC by fixing your registry

The shortcut isn't running wrkgadm.exe. It's using the /wrkgrp switch to
tell Access to over-ride the default mdw and use your secure mdw for that
session.

If the login doesn't come up, then the Admin user in the workgroup file
doesn't have a password set. That is what causes the login to appear.

You said that you used the Workgroup Administrator to join your secure mdw.
It sounds as though you didn't set a password for the Admin user.


--
Joan Wild
Microsoft Access MVP

RoadKyng wrote:
I was wondering if a runtime solution could be done due to the
restriction you pointed out. So the shortcut needs to run the
wrkgrpadmin.exe ?

Now, as to my other issue, the login for the database does not come
up. The error message pops after Access loads. The problem may be a
Domain issue as this is across two seperate Domains. Although I have
verified the users have permissions across the Domains.
And if I come to a computer inside our Domain and use the Access
login I established for the problem users, it works fine. I deployed
this DB to users inside our domain and did not have a problem.
--
GmH


"Joan Wild" wrote:

That is an Access permissions error by the sound of it, so it means
that the Access username used to log in to the database doesn't have
Open/Run permissions on the Database Object. Or that the Group(s)
that user belongs to doesn't have permission. It isn't related to
the 'machine'.

Does the username/password dialog come up when they open the mdb?

You don't actually need, or necessarily want, to join the PC to the
secure workgroup by default. They may have other Access databases
that haven't been secured. By making the secure mdw the default,
they'll need to login for *every* database.

Instead, leave them joined to the standard system.mdw that ships with
Access, and provide a desktop shortcut that points to the secure mdw
to be used for just that session. The target would look like
"path to msaccess.exe" "path to frontend mdb" /wrkgrp "path to
secure mdw"

--
Joan Wild
Microsoft Access MVP

RoadKyng wrote:
The back end file is on a Public share on our server. I have
confirmed the client machine has permissions.
I was able to join the workgroup for the client machine (the
workgroup mdw file is also in the Public share).
I installed the database front end on the client machine but it will
not open the database. Message says the machine/user does not have
the permissions. I have ensured this user has the rights to the
database.

Is this a network issue or Access issue?
--
GmH


.

Relevant Pages

  • Re: Workgroups and XP
    ... > I have an Access 97 database that uses the workgroup ... > the workgroup useing the join utility. ... That would use the secure mdw for all their Access sessions, ...
    (microsoft.public.access.security)
  • Re: table pesmissions
    ... That table was created while you were joined by default to some secure mdw. ... You need to open your database using that mdw and then assign permissions to ... the Users Group for the table. ...
    (microsoft.public.access.security)
  • Re: Netowrk use cant open database
    ... Joan, you're awesome! ... You said that you used the Workgroup Administrator to join your secure mdw. ... Now, as to my other issue, the login for the database does not come ... Open/Run permissions on the Database Object. ...
    (microsoft.public.access.security)
  • Re: Error opening database with shortcut
    ... You can use the workgroup administrator and make your secure mdw the default ... However you'll then have to login for every database. ... Microsoft Access MVP ...
    (microsoft.public.access.security)
  • Re: Netowrk use cant open database
    ... That is an Access permissions error by the sound of it, ... Access username used to log in to the database doesn't have Open/Run ... and provide a desktop shortcut that points to the secure mdw to be ... I was able to join the workgroup for the client machine (the ...
    (microsoft.public.access.security)