Sarah
There is a very good article about using User Level Security at http://support.microsoft.com/kb/207793/en-us
It gives very specific instructions. Once you've gone through it and fixed your USL read my article on fixing some issues with ULS titled "User Level Security Not Behaving? How to Fix It" at http://www.thatlldoit.com/Pages/howtosarticles.aspx
Sorry the page links are not working. My host (Microsoft) moved from Office Live to Office 365 and messed up all the HTML. One of these days I'll get some time off to re-work my site.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
--- In MS_Access_Professionals@yahoogroups.com, <ms_access_professionals@yahoogroups.com> wrote:
I currently have a split database in Access 2003, every user has their own front end and they share one back-end. In the shortcut that opens the database, their is a reference to a workgroup that prompts for user name and password before they can open the application. However if the user modifies the shortcut and removes the reference to the workgroup, they can bypass the security. How do I prevent this?.
The shortcut looks currently like this:
'"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /wrkgrp "G:\demo\demo.mdw" "G:\demo\demouser1.mde" /CMDG:\demo\demo.MDB'
If they user changes it to this, they can bypass 'security':
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "G:\demo\demouser1.mde" /CMDG:\demo\demo.MDB'
How can I prevent this?.
As always thanks in advance for all your input.
Sarah
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (10) |
Tidak ada komentar:
Posting Komentar