Netowrk use can't open database

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

RoadKyng - 27 Apr 2006 21:49 GMT

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?

Signature

GmH

Reply to this Message

John Mishefske - 28 Apr 2006 06:51 GMT

> The back end file is on a Public share on our server. I have confirmed the
> client machine has permissions.
[quoted text clipped - 5 lines]
>
> Is this a network issue or Access issue?

Is the Front End doing a Compact On Close? Try disabling that.

http://support.microsoft.com/default.aspx?scid=kb;en-us;295234

Signature

'---------------
'John Mishefske
'---------------

Reply to this Message

RoadKyng - 28 Apr 2006 14:51 GMT

Not sure.

I have not set this up and am unsure where to do it.

I do make it a habit to manually compact every few days or so. However the
errors detailed in the kb article don't appear to match what I am getting. I
will however follow the steps suggested and see if that is what is happening.

thanks

Signature

GmH

> > The back end file is on a Public share on our server. I have confirmed the
> > client machine has permissions.
[quoted text clipped - 9 lines]
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;295234

Reply to this Message

Joan Wild - 28 Apr 2006 17:48 GMT

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"

Signature

Joan Wild
Microsoft Access MVP

> The back end file is on a Public share on our server. I have
> confirmed the client machine has permissions.
[quoted text clipped - 7 lines]
> --
> GmH

Reply to this Message

RoadKyng - 28 Apr 2006 19:29 GMT

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.

Signature

GmH

> 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
[quoted text clipped - 24 lines]
> > --
> > GmH

Reply to this Message

Joan Wild - 28 Apr 2006 19:56 GMT

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.

Signature

Joan Wild
Microsoft Access MVP

> I was wondering if a runtime solution could be done due to the
> restriction you pointed out. So the shortcut needs to run the
[quoted text clipped - 45 lines]
>>> --
>>> GmH

Reply to this Message

RoadKyng - 29 Apr 2006 01:21 GMT

Joan, you're awesome! And I bet you can cook and are good looking too!

I'll implement your suggestions on Monday. I know I did not set one up for
the Admin user. I followed the whitepaper (I thought) but must have missed
something

Thanks a bunch

gavin hill

Signature

GmH

> 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
[quoted text clipped - 55 lines]
> >>> --
> >>> GmH

Reply to this Message