Re: Microsoft has utterly failed with Access 2007

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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: Workgroup information file problem
    ... the workgroup administrator to check which workgroup you're joined to, ... database pretty much like the one I already created for company one. ... lot of playing around with the various permissions on various objects. ... shift key while double clicking on the file name instead of the shortcut? ...
    (microsoft.public.access.security)
  • Re: Permission denied after upgrade!
    ... After the reinstallation of Access XP, the assigned workgroup information ... default user, "Admin," which may, indeed, not have enough permissions. ... enabling the database for use in the Access XP environment. ... If you install Access 97 and Access 2K and don't take the ...
    (microsoft.public.access.security)
  • Re: Database Ruined
    ... the permissions to access/update the tables. ... In a properly secured database, only the owner of that database has ... use the exact same settings when recreating the workgroup. ... If this should be the Admin user of the workgroup (it shouldn't be ...
    (microsoft.public.access.security)
  • Workgroup information file problem
    ... I have a split database that employs USL. ... When I select the short-cut, I’m prompted for my username and password. ... I was joined to the SYSTEM.MDW workgroup! ... permissions, I see all the new users I created and all the permissions I ...
    (microsoft.public.access.security)
  • Re: Becoming the Owner
    ... The owner isn't the only user who can set permissions on objects. ... you've logged into a database that was created using a different workgroup ...
    (microsoft.public.access.security)