Re: Secured Database works exactly right on one computer, but on another not quite r

Joan Wild wrote:
I set up user-level security on an Access 2003 DB on a Windows XP
machine, using the security wizard. I'm almost positive that I
[quoted text clipped - 7 lines]
edit or add data. All the other users can log on fine, but not edit
data.

It sounds as though you tinkered with permissions after running the wizard
(or perhaps ran the wizard a second time?).
I assume you're talking permissions in the security...no, I didn't.

You say your username has
access to the objects, but you can't edit/add data. What do you mean by
access?
I can create, delete, and edit forms, queries, reports, macros, etc....
everything except data. The other users can't, which is as it should be.
Even the admin account can't edit data.

What permissions does the full data group have on the data sources
of your forms?

You can check this in Tools, security, permissions.
Read design, Read data, Update data, Delete data, on both machines
I have looked at Security on both machines and it appears to be identical...
the SAME FILE.

In desperation, I copied the FE to my second Windows 2000/Office 2003
machine, from which I was planning to demo anyway, and it works
perfectly there! The first few times I copied the 'master' to the
second machine, I held my breath, afraid that it would not work, but
it always does. It really looks like it's the MACHINE, not the
setup, but I just don't see how that could be.

Sounds like you might be using a different mdw file on the problem machine.
I don't see how that is possible. I only created one security file. When I
look at security from either machine, I see all the users and the permissions
look to be identical. Yesterday, I added a user, and I see him from the
security menu on both machines.

Both shortcuts point to the same security file.

On my machine, the shortcut is:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\Documents and
Settings\Jessica\My Documents\MasterGardeners\DataBase\MasterGardeners.mdb"
/wrkgrp "C:\Documents and Settings\Jessica\My Documents\MasterGardeners\
DataBase\Security.mdw"

On the other:
"C:\Program Files\Microsoft Office 2000\OFFICE11\MSACCESS.EXE" "C:\MAMG\
MasterGardeners.mdb" /WRKGRP "M:\Security.mdw"
M: is mapped to "C:\Documents and Settings\Jessica\My Documents\
MasterGardeners\DataBase" on my machine.

My shortcut on the second machine is "C:\Program Files\Microsoft
Office 2000\ OFFICE11\MSACCESS.EXE" "C:\MAMG\MasterGardeners.mdb"
/WRKGRP "M:\Security. mdw". M: is mapped to the folder on my
machine.

Try using UNC pathname for the security.mdw.
\\machinename\path\security.mdw
It's the remote machine that works properly, using the reference to M:. On
my machine everything is in the same folder in My Documents... no reason to
use UNC there.

You have some extra spaces in your shortcut
that shouldn't be there like 2000\spOFFICE11 and alos Security.spmdw
There is actually a space in the folder name for Access (there are quotes);
not sure why there appears to be a space in the mdw in the post; it is not
there.......I copied/pasted then just like I did above just now.

The data is linked to the BE on my machine. I realized in
researching this problem that I also need to join the BE to the
workgroup, but I'm waiting until I get this resolved.

In that case, the problem is with the permissions in the FE or the wrong
shortcut or wrong mdw for the FE. Since the BE is secured, anyone with any
mdw can read the data.

I agree with you about where it appears the problem is....but I am copying
the FE from my machine to the other one, and referencing the same mdw. I
don't see any possibility that both machines are not using the same security.
mdw. I did a search on my entire C: drive for *.mdw, and found only this one,
two other ones with completely different names that I use (successfully) for
other DB's. Actually, I was expecting to see the default system.mdw that
everything I read said not to use, but didn't find it.

What it looks like to me is that it's related to the MACHINE, although I
don't see how that could be...

I understand that the BE is exposed. I'm going to join it to the same
security as soon as I get this resolved. Right now, editing the BE directly
is the only way I can edit the data on my machine.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200611/1

.

Relevant Pages

  • Re: Front end, Back end, and restrictions on which Forms can open.
    ... I'm thinking that it isn't usng the correct mdw during the wizard. ... ensuring that 'users' were granted no permissions (as i did when i was ... Joan Wild wrote: ... using the same method and selecting the same security file. ...
    (microsoft.public.access.security)
  • Re: RWOP queries for back-end secuirty: easy/hard? slow/fast?
    ... MDW file in a way that prohibits the creation of new databases. ... my understanding of Jet security would ... permissions, which are all stored in particular MDB files. ... ability to create a new database does not give someone the ability ...
    (comp.databases.ms-access)
  • RE: What server hardening are you doing these days?
    ... permissions on their data, and Microsoft encourages ISVs to minimize ... I've been able to discuss ACLs and other security issues in Windows with ... Control or DAC (which is what you're referring to by the "stupid ...
    (Focus-Microsoft)
  • Re: Usurped Creator of Database
    ... The security appeared to work well until I used the wizard to increase the ... fine until I added permissions to the regular users (people without a special ... You need to secure it manually. ...
    (microsoft.public.access.security)
  • Re: Administrator cant add users
    ... The Users Group is common to all mdw files, so normally doesn't have any permissions. ... It sounds as though someone just went in and started added usernames to the standard mdw that ships with Access. ... Are there any other Groups and/or Users when you look at Tools, Security, Accounts? ... If you start Access and create a new mdb, can you then use File, Get External Data and import all the objects from your mdb? ...
    (microsoft.public.access.security)
Loading