Re: Microsoft has utterly failed with Access 2007

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

You've misinterpretted what John's suggesting.

You can use Access 2007 and still have User Level Security as long as you
don't convert your applications from MDB files to the new ACCDB format.

I can't answer on Microsoft's behalf, but Access User-Level Security really
wasn't very secure. Like a screen door, it may have kept honest people out,
but anyone who wanted to get at the data could do so without any trouble.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Amy E. Baggott" <AmyEBaggott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:24B84030-87CE-4B3D-9A2D-3A4DA49DE326@xxxxxxxxxxxxxxxx
That's exactly what we have. We installed Office 2007 with the exception
of
Access, which we left at 2003. However, there are some features of Access
2007 that would be really useful (such as filtering reports on the fly
instead of having multiple versions of one report depending on how you
want
it filtered and/or sorted) that you can't use if it stays in Access 2003.
Also, it means we have to make sure import/export files get converted to
the
right version. Any idea why MS did away with user-level permissions?
They
are incredibly useful in a mult-user, multi-skill-level environment.
--
Amy E. Baggott

"I''m going crazy and I''m taking all of you with me!" -- Linda Grayson


"John Spencer MVP" wrote:

I believe that as long as you leave the database in Access 2003 format
and do
not convert it to an AccDB that you can still use user-level security on
the
database. The NEW format does not support user0level security.

John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County

Amy E. Baggott wrote:
What I want to know is why Microsoft did away with user-level security
and
workgroups in Access 2007. This is the primary reason we have not
converted
our database from Access 2003. Before we set up a workgroup with
user-level
permissions, the database kept crashing (sometimes several times a
day), and
we never could figure out why. Implementing the workgroup not only
solved
that, but has other advantages as well. I can limit permission to
modify the
design of database objects to the couple of people who actually know
what
they are doing. Also, I can set permissions so that the users who are
actually creating and managing the orders can modify the data, but I
have
some users who need to see certain data, but I don't want them to
actually
touch it. From what I have been told both by our IT people and a
seminar I
went to on converting Access 2003 databases to Access 2007 or SQL
Server,
Access 2007 has no way to set permissions at the user and object level.
Please tell me I am wrong and tell me how to go about it.



.

Relevant Pages

  • Re: Creating security for MS Access application
    ... I wanted to create user ids and grant permissions based on user ids. ... You've not properly secured your database if that's the case. ... of User Level Security before mucking around with it too much more. ... with instructions on how to properly secure a database without the Security Wizard: ...
    (microsoft.public.access.security)
  • Re: A note to add to ASPFAQ.com for database compacting
    ... I set the database directory permission to give full access to ... then checked "Allow inheritable permissions from parent to ... Thus your problem is that you have to high of security set ... > the files needed and also a compact & repair operation will not cause ...
    (microsoft.public.inetserver.asp.db)
  • Sorting out security
    ... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
    (microsoft.public.access.security)
  • RE: Security setup does not allow import of tables
    ... When you click on the menu option Tools> Security> User and Group ... Permissions at the bottom of the screen does it show you logged in as the ... | new system database that has a unique Name, Organization, ... In the User and Group Accounts dialog box, ...
    (microsoft.public.access.security)
  • Re: Access db accessibility (permissions??)
    ... if you have not then your computers are workgrouped, security becomes a bit ... password when you first login to your database. ... > folder and then delete it. ... So the permissions are RWED on that folder. ...
    (microsoft.public.access.security)