• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 615
  • Last Modified:

Microsoft Access MDW file keeps losing all security settings

We are still using the .mdw file in our Access 2010 frontend.  For some reason the mdw file keeps losing all the security settings and I have to go back in and set them.

Any ideas why?

Any way to stop this?
0
J.R. Sitman
Asked:
J.R. Sitman
3 Solutions
 
MacroShadowCommented:
Access 2010 no longer supports Workgroup security (User-Level Security).
0
 
J.R. SitmanAuthor Commented:
I understand that, however, I'm not using the ACCDB so my mdw file is still working with my .mdb frontend.
0
 
PatHartmanCommented:
Workgroup security was deprecated 7 years ago.  Perhaps now is the time to give it up.  Instead of trying to figure out why it doesn't work correctly, it might be better to spend the time to replace it with your own model.

Even though I rarely used workgroup security (it was a real PITA to implement correctly), I would have preferred that the Access team make it easier to understand but they choose to get rid of it instead after convincing themselves that its purpose was data security which as far as I could see wasn't the reason for using it at all.  If you need data security, Jet and ACE are poor choices since you can simply pick up the file and take it home where you can work on breaking into it at your leisure.   Workgroup security was always about managing the interface as far as I understood it.  There is no plug in replacement but there are models that are not too hard to implement if you can define some of your requirements.  Think about it positively, with a custom solution, you can make it do what you want.
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
J.R. SitmanAuthor Commented:
You are correct.  Time to bite-the-bullet.  I have a developer that I'm working with that can help me.
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Note ... if ... you were in MDB format in A2010, ULS is still supported.
0
 
MacroShadowCommented:
Try creating a shortcut to your FE, using the  /wrkgrp switch. Something along the lines of: "C:\Program Files\Microsoft Office\Office\MSACCESS.exe" "C:\Test\YourDatabase.mdb" /WRKGRP "C:\Test\Secure.mdw"

Where "C:\Program Files\Microsoft Office\Office\MSACCESS.exe" is the path to Access.
"C:\Test\YourDatabase.mdb" is the path to your mdb and "C:\Test\Secure.mdw" is the path to your mdw file.
0
 
J.R. SitmanAuthor Commented:
I selected the incorrect solution.  How do I fix it?
0
 
MacroShadowCommented:
Click on the request attention button under the question.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
Just to add one comment, watch out if you've called your custom "system.mdw".

While it's been advertised that security was removed from A2007 and up, it really was not.

All Microsoft does is remove all the ACL's (Access Control Lists) in a database when you convert it to an ACE format. The other thing they did was hide all the interface elements.

But JET workgroup security is still on and working and a MDW file is still used.   It's just the default standard one and if you have not renamed your custom MDW file to something other than 'system.mdw', it will get over written when using A2007 and up.

Jim.
0
 
J.R. SitmanAuthor Commented:
@marcoshadow, that's how I have it set up. Thanks
0
 
J.R. SitmanAuthor Commented:
Thanks
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now