Permissions problem

[Leslie Isaacs]

Hello All

I have a split fe/be a2k database.
Until recently, all the fe's were on PCs running w2k.
The fe is secured.
The shortcut on users' desktops has the following target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "C:\wkhc
database\telnumbers.mdb" /wrkgrp "\\clinical\public\secured.mdw"

.... which has always worked fine.

We now have a windows xp PC, on which I have edited the shortcut target to
the following:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\wkhc
database\telnumbers.mdb" /wrkgrp "\\clinical\public\secured.mdw"

On this PC, however, the permissions that I can see (under
Tools>Security>Permissions) are different from those I can see from the
other PCs: in fact, as the 'owner' of all the db objects and a member of all
the groups, I am the only person with permission to do anything - including
opening the initial splash screen. I cannot understand this, as both the
shortcuts above refer to the same workgroup file
(\\clinical\public\secured.mdw). It seems that the OS of the PC affects the
permissions in some way?

I hope someone can help, as more windows xp PCs are due and this will cause
us significant problems.

Many thanks
Leslie Isaacs

 

[TC]

The OS permissions do not affect th Access permissions except in one
regard: each user needs full read/write/create/delete permissions to
the folder where the database file resides. Otherwise, the database
might only be opened in read-only mode.

You realize that the permissions aren't stored in the workgroup file -
they're only stored in the database file? Only the user & group names,
& user/group relationships, are stored in the workgroup file. So, using
the same workgroup file, is only one part of the equation.

HTH,
TC

 

[Leslie Isaacs]

Hello TC

Thanks for your reply.

Apologies for my ignorance, and I realise I may now be directing this to the
wrong ng, but when you say "each user needs full read/write/create/delete
permissions to
the folder where the database file resides", does this relate to the
frontend or the backend or both - and how do I set these permissions?

Thanks for your continues help.
Les

 

[Leslie Isaacs]

Hello TC

Thanks for your reply.

Apologies for my ignorance, and I realise I may now be directing this to the
wrong ng, but when you say "each user needs full read/write/create/delete
permissions to
the folder where the database file resides", does this relate to the
frontend or the backend or both - and how do I set these permissions?

Thanks for your continues help.
Les

 

[TC]

Hi Les

No, your question is quite on-topic for this newsgroup IMO.

The permissions I was referring to are set through the Windows user
interface. I think (from memory) that you right-click the folder & use
the "Permissions" option. But I only have win 98 here, so if that's
wrong, someone please hop in & correct me.

I believe you would have to set those permissions on the folder(s)
containing:

- the front end, AND
- the back end, AND
- the workgroup information file,

since each of those three files will normally create a corresponding
..LDB file while it is open.

I haven't had much personal experience in using "locked down"
environment where wrong permisions can cause problems. So, anyone else
please feel free to correct this post if appropriate!

Here's an article with further information:
http://support.microsoft.com/kb/q136128/

HTH,
TC

 

[TC]

PS. ignore that the article is only relevant to Access 95 & 97. Most or
all of it applies to later versions also.

HTH,
TC