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

JessicaMorris 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
tested it and it worked correctly at the very beginning.

On my machine, I am prompted for user id/password, and only those set
up are allowed. Some users are read only and some are full data. I
have a FE/BE set of DB's. The 'master' FE, BE, and mdw file are on
my Windows XP (completely current) machine. Only I have access to
the objects, which is correct, but no one, not even me or ADMIN can
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?). You say your username has
access to the objects, but you can't edit/add data. What do you mean by
access? What permissions does the full data group have on the data sources
of your forms? You can check this in Tools, security, permissions.

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.

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 You have some extra spaces in your shortcut
that shouldn't be there like 2000\spOFFICE11 and alos Security.spmdw

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.

--
Joan Wild
Microsoft Access MVP


.

Relevant Pages

  • Re: Form Permissions Disappear
    ... How do I set the permissions for the form and combo box record sources? ... I add new userduring the Wizard process and then ... I then exit and, using the desktop shortcut, log back in under one of the ... Am I correct in re-running the User-Level Security wizard each time I ...
    (microsoft.public.access.security)
  • Re: disable wizards with workgroup permissions on Access2000?
    ... One approach is to lock down your application, ... I used the security wizard, ... That doesn't affect their permissions regarding creating new objects, ...
    (microsoft.public.access.security)
  • Re: More ULS Problems
    ... Group permissions and FIND OUT which user or group has such permissions when ... One of the criticisms of Security Wizard, apart from potential bugs in the ... full understanding of ULS. ...
    (microsoft.public.access.security)
  • Re: Form Permissions Disappear
    ... I believe that during the wizard process, you can choose not to create a desktop shortcut. ... If you don't have the permissions checked that you had previously, it may be removing that permission. ... Am I correct in re-running the User-Level Security wizard each time I ... "Joan Wild" wrote: ...
    (microsoft.public.access.security)
  • 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)
Loading