Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Security / August 2007

Tip: Looking for answers? Try searching our database.

Setting 2003 ULS permissions won't stick using 2007

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jacques Latoison - 09 Aug 2007 20:48 GMT
We have an MDB that is in the Access 2003 format.  It uses User Level
Security and has worked well for some time.
After upgrading the staff with Access 2007, it still works fine.

I now need to make some permissions changes, and although 2007 will let me
view it, and change it on the screen, nothing actually sticks - it doesn't
actually do the work in the background, even though its doing it on the
screen.

Any suggestions are helpful...
Scott McDaniel - 10 Aug 2007 11:02 GMT
>We have an MDB that is in the Access 2003 format.  It uses User Level
>Security and has worked well for some time.
[quoted text clipped - 6 lines]
>
>Any suggestions are helpful...

Are you SURE that you're joined to the correct workgroup when making these changes? I'm not overly familiar with 2007,
but in 03 you would open Access and click Tools - Security - Workgroup Administrator ... or you can open your VB edit
window, then the Immediate window and type this:

?dbengine.systemdb

This would show the workgroup you're currently using ... make sure it's the correct workgroup.

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
Jacques Latoison - 13 Aug 2007 14:26 GMT
Yes I'm sure.
The DB's are opened with a shortcut that uses that workgroup.
The DB's are not opened by clicking directly on the DB's themselves.

There are several DB's that use the same workgroup, and its the only
workgroup file on the network.

>>We have an MDB that is in the Access 2003 format.  It uses User Level
>>Security and has worked well for some time.
[quoted text clipped - 21 lines]
> scott@takemeout_infotrakker.com
> www.infotrakker.com
Joan Wild - 13 Aug 2007 19:14 GMT
Could you be more specific.  What makes you think the permission changes are not sticking?  Remember that the permissions are stored in the mdb file.  Once you make permission changes, you need to distribute the updated frontend to the users.

Only the usernames/passwords/groups/memberships are stored in the common mdw.

Signature

Joan Wild
Microsoft Access MVP

> Yes I'm sure.
> The DB's are opened with a shortcut that uses that workgroup.
[quoted text clipped - 28 lines]
>> scott@takemeout_infotrakker.com
>> www.infotrakker.com 
Jacques Latoison - 21 Aug 2007 14:14 GMT
When I go back into the permissions window, after completely leaving it,
they aren't changed.
When I had to give someone access to something, it would never work.
When I checked it from an older machine running Access 2003, it wasn't
changed.
When I changed it from that Access 2003 machine, it worked.

Could you be more specific.  What makes you think the permission changes are
not sticking?  Remember that the permissions are stored in the mdb file.
Once you make permission changes, you need to distribute the updated
frontend to the users.

Only the usernames/passwords/groups/memberships are stored in the common
mdw.

Signature

Joan Wild
Microsoft Access MVP

> Yes I'm sure.
> The DB's are opened with a shortcut that uses that workgroup.
[quoted text clipped - 34 lines]
>> scott@takemeout_infotrakker.com
>> www.infotrakker.com
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.