Re: User level security 2002 / 2003

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Cfox4 wrote:
I've got an XP2002 db that I secured via user level security. My
problem is that my XP2003 users cannot open forms. They get the error
"you do not have open/run priveleges on form"

I've had those same 2003 users log into the db on a 2002 machine and
they are able to open the forms. Is there a file format issue here?
Any ideas? .mdw compatibility issues?

Are they using your secured workgroup (MDW) file? If not, then your actual
problem is that you didn't apply security properly in the first place. Usually
this would result in no security at all, but in your case the security "hole" is
only letting then into the file, but is at least stopping them at the forms.

One of the more common mistakes when applying security is leaving "Admin" as the
owner of the database and some or all of the objects. As owner Admin will be
allowed in even though he has no "permissions". Any objects that you created
after securing the file would not be owned by Admin so someone opening the file
with the wrong workgroup would not be able to use those objects.

You should start over with your security until you achieve the proper behavior
which is that someone using the wrong workgroup is not able to open the file at
all. Then you can give all users a shortcut for your file that specifies the
correct workgroup as a command line argument. Using that shortcut they would be
prompted to log in and should be granted the permissions assigned to the account
they use.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com


.



Relevant Pages

  • Re: i give up...please tell me how to remove security
    ... Access Security: www.ltcomputerdesigns.com/Security.htm ... > When I copied the database over I also copied the "secured.mdw" file and ... > shortcut that I used to open it. ... I changed the workgroup in the target of the shortcut to refer to this ...
    (microsoft.public.access.security)
  • Re: Integrating Access security with user options
    ... truly secure this stuff without native Access security. ... How might one attach other options not inherent to Access security to ... This might be as simple as using the built-in workgroup ... > workgroup file or your users will not be able to open the app. ...
    (microsoft.public.access.security)
  • Re: Integrating Access security with user options
    ... user security, such as user-based/user-settable options. ... I enable/disable various controls based on group membership. ... This might be as simple as using the built-in workgroup ... workgroup file or your users will not be able to open the app. ...
    (microsoft.public.access.security)
  • Re: Workgroup file for one db only (not to apply to other dbs)
    ... I just had to create a new db with user-level security. ... I can use a shortcut ... workgroup file or have to use a shortcut either as their ms access folders ... create different shortcuts on the basis of their access folders. ...
    (microsoft.public.access.security)
  • Re: Integrating Access security with user options
    ... I enable/disable various controls based on group membership. ... How might one attach other options not inherent to Access security to ... This might be as simple as using the built-in workgroup ... workgroup file or your users will not be able to open the app. ...
    (microsoft.public.access.security)