December 21, 2012 at 4:19 pm
We've been using Workgroup for more years than I have toes. In Access 2010 when I use the DoCmd.RunCommand acCmdWorkgroupAdministrator I can create a new group or join an existing MDW file. I want to view the Access users and reset a few passwords. There must be an easy way to do this, but after trolling through the web for more than an hour I am stuck.
Can someone PLEASE help?
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
December 21, 2012 at 4:45 pm
And there is. Open your database so the Navigation Pane is visible, and then choose File on the ribbons. In the center you should see three large buttons. The top one does the Compact & Repair, the second one lets you manage Access User Security and is labels "Manage User & Permissions" - click that one and choose User and Group Accounts and you will see the familiar dialog box from prior versions.
Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
December 24, 2012 at 12:41 pm
It was the &&**( shift key. All is good now.
Access is not my friend.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
December 26, 2012 at 9:54 am
Access is my friend. That said, however, I have no idea why Microsoft chose to dump all the security features Access used to have. That probably contributed to your difficulty. If anyone can explain Microsoft's reasoning, I would be glad to hear it. Although I still am a big fan of Access in the right circumstance, it isn't in my view as good as it used to be.
December 26, 2012 at 10:20 am
Most of our stuff was converted to a COTS product, but we still have a few legacy apps that use Access as a front end.
I worked on these many years ago, so when they go to sh&t I have to bail out our users.
I have many other activities that are more entertaining. Like getting a root canal.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
December 26, 2012 at 8:36 pm
RonKyle (12/26/2012)
Access is my friend. That said, however, I have no idea why Microsoft chose to dump all the security features Access used to have. That probably contributed to your difficulty. If anyone can explain Microsoft's reasoning, I would be glad to hear it. Although I still am a big fan of Access in the right circumstance, it isn't in my view as good as it used to be.
Well, they didn't exactly dump all the security features they had in older versions, BUT - the people who did tech support kept complaining about all the Access users who tried to use their security features and locked them up so they couldn't get in, or they thought they had things locked up and discovered they were wide open if you knew what to do. So they created a new database engine (the ACE engine) in Access 2007 that didn't support the security feature, and they put the menu's for managing the legacy JET applications in obsucre places hoping we woulde never find them.
Seriously, what the folks who direct the Access development program failed to understand was that the most useful feature of the security feature is the ability to tell who the user is, so problem users can be identified and/or restricted. The developments we continue to do are all based on .MDB front-ends connecting to a SQL Server back-end - which gives us the ability to create robust applications that support large numbers of users. And we still use Access User Security to determine who gets to do what.
Wendell
Colorful Colorado
You can't see the view if you don't climb the mountain!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply