![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, Do I still have to use the .mdw file to run security for the accdb? I can't find how, but my old mdb will still prompt for a user/password even if opened from the file explorer. Can't seem to set this up with accdb. Any pointers would be useful, thanks. |
#3
| |||
| |||
|
|
No. User/group security is still available but only with MDB/MDE, not with the newer ACCDB files. -- Larry Linson Microsoft Office Access MVP Co-Author, Microsoft Access Small Business Solutions, Wiley 2010 "fearless55" <james (AT) pigottsinvestments (DOT) co.uk> wrote in message news:8699df5c-8855-4c1e-a504-27eb0e03a8b0 (AT) googlegroups (DOT) com... Hello, Do I still have to use the .mdw file to run security for the accdb? I can't find how, but my old mdb will still prompt for a user/password even if opened from the file explorer. Can't seem to set this up with accdb. Any pointers would be useful, thanks. |
#4
| |||
| |||
|
|
No. User/group security is still available but only with MDB/MDE, not with the newer ACCDB files. Wow! What can we do to protect access to certain forms etc? |
#5
| |||
| |||
|
|
On Wednesday, August 22, 2012 11:53:06 PM UTC+1, Access Developer wrote: No. User/group security is still available but only with MDB/MDE, not with the newer ACCDB files. -- Larry Linson Microsoft Office Access MVP Co-Author, Microsoft Access Small Business Solutions, Wiley 2010 "fearless55" <james (AT) pigottsinvestments (DOT) co.uk> wrote in message news:8699df5c-8855-4c1e-a504-27eb0e03a8b0 (AT) googlegroups (DOT) com... Hello, Do I still have to use the .mdw file to run security for the accdb? I can't find how, but my old mdb will still prompt for a user/password even if opened from the file explorer. Can't seem to set this up with accdb. Any pointers would be useful, thanks. Wow! What can we do to protect access to certain forms etc? |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
"fearless55" wrote No. User/group security is still available but only with MDB/MDE, not with the newer ACCDB files. Wow! What can we do to protect access to certain forms etc? I'm certainly not the best authority on the subject of security . . . Access security has, in every version, been sufficiently weak that you could search the Internet and find "breaker" code. Sergei Gavrilov (who creates, publishes, and sells some good Access software tools) gave up on selling breaker code and published a free version that didn't even require the MDW file, just to show it could be done. Since I realized that Access security didn't protect much of anything, I didn't exert myself to try to create a secure database. Most of my "paid" work used a server database of one brand or another and data security relied on the server DB's security -- but, you are correct that doesn't let you use security to block access to forms. Also, the vast bulk of what I did was "bespoke systems" (systems created for a specific client for their own internal use, accessible only to/by their employees) and for "sensitive" data, we might create a separate database that was distributed only to those employees who should have access. Although there has been (and still is) code that can be demonstrated to extract code from MDE or ACCDE, it is not as common as heavy-duty "security breaker" code, so a combination of code, compilation to MDE or ACCDE, and your own security might be sufficient. I did not join in the mass weeping, wailing, and gnashing of teeth over the loss of Access security, because it had not (I thought, and still think) been really worth the effort to implement it in your databases anyway. Sorry that I can't offer you a good workaround security option, but every one I've seen was quickly broken by those who had an interest in such. Larry Linson Microsoft Office Access MVP Co-Author, "Microsoft Access Small Business Solutions", pub by Wylie, 2010 |
#8
| |||
| |||
|
|
"fearless55" wrote No. User/group security is still available but only with MDB/MDE, not with the newer ACCDB files. Wow! What can we do to protect access to certain forms etc? I'm certainly not the best authority on the subject of security . . . Access security has, in every version, been sufficiently weak that you could search the Internet and find "breaker" code. Sergei Gavrilov (who creates, publishes, and sells some good Access software tools) gave up on selling breaker code and published a free version that didn't even require the MDW file, just to show it could be done. Since I realized that Access security didn't protect much of anything, I didn't exert myself to try to create a secure database. Most of my "paid" work used a server database of one brand or another and data security relied on the server DB's security -- but, you are correct that doesn't let you use security to block access to forms. Also, the vast bulk of what I did was "bespoke systems" (systems created for a specific client for their own internal use, accessible only to/by their employees) and for "sensitive" data, we might create a separate database that was distributed only to those employees who should have access. Although there has been (and still is) code that can be demonstrated to extract code from MDE or ACCDE, it is not as common as heavy-duty "security breaker" code, so a combination of code, compilation to MDE or ACCDE, and your own security might be sufficient. I did not join in the mass weeping, wailing, and gnashing of teeth over the loss of Access security, because it had not (I thought, and still think) been really worth the effort to implement it in your databases anyway. Sorry that I can't offer you a good workaround security option, but every one I've seen was quickly broken by those who had an interest in such. Larry Linson Microsoft Office Access MVP Co-Author, "Microsoft Access Small Business Solutions", pub by Wylie, 2010 |
![]() |
| Thread Tools | |
| Display Modes | |
| |