Graham - I completely agree. I got really good at setting up ULS and that meant less reliance on coding. But as I slowly had to move away from ULS I developed methods for handling permissions. A lot of it was encryption. So much re-inventing of the wheel.
---In MS_Access_Professionals@yahoogroups.com, <graham@mandeno.com> wrote :
Hi Bill
I think it was a very sad day when MS decided to kill off ULS. Sure, it could be broken, but it was another level of protection, and at least it required some tool other that VBA to break it.
Cheers,
Graham
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Saturday, 21 July 2018 10:43
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Database protection
Graham – I don't know how to prevent that. My Properties Setter can do exactly that albeit only temporarily if it's a ACCDE or MBE having startup form code that sets the AllowBypassKey to No. This is why I don't rely on Access for security. There are too many holes that a developer can leverage.
All my applications have SQL Server back ends that users cannot get directly into. I take other measures to protect tables from users who might set the AllowBypassKey to Yes, but I can't discuss those methods due to company security policies.
Regards,
Bill Mosca
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Thursday, July 19, 2018 4:52 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Database protection
Hi Bill
Just curious – how could you stop some smart-arse from writing some external code to turn on AllowBypassKey, then opening the database with the shift key?
Best…
Graham
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Friday, 20 July 2018 05:04
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Database protection
Just for clarification...Workgroups (User Level Security) only work for MDB files such as Access 2003 and earlier. They are not available for ACCDB files. From what I understand, MS decided to do away with ULS because it really wasn't that secure. Unfortunately, they didn't replace it with something new. We developers had to come up with our own homegrown security that relies heavily on code.
One project I had needed to be converted to an Access 2010 file so I spent a good month writing the code to use Active Directory authentication and then code all forms/reports security based on the username and group. Yes, it's more secure unless someone has shared his username and password to his AD account, but it was a real pain.
Regards,
Bill Mosca
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Tuesday, July 17, 2018 2:09 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: RE: [MS_AccessPros] Database protection
On a more granular level, you can choose Tools/Security/"Workgroup and User Permissions".
This will let you set specific permissions for each table and each user or group. Just make sure you are the admin with full permissions.
This assumes that users need to log in using their username/password.
Gary
At 04:22 PM 7/17/2018, you wrote:
You can put a password on the database I think it is on the file menu?
Respectfully,
[RCEmailSigLogo]
Liz Ravenwood
Data Technologies
Interior Systems
Rockwell Collins
1851 So. Pantano Rd, Tucson, AZ 85710 USA
(520) 239-4808
Liz_ravenwood@beaerospace.com< mailto:Liz_ravenwood@beaerospace.com>
rockwellcollins.com< http://www.rockwellcollins.com/>
From: MS_Access_Professionals@yahoogroups.com [ mailto:MS_Access_Professionals@yahoogroups.com]
Sent: Tuesday, July 17, 2018 12:58 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: [MS_AccessPros] Database protection
I want to know how to prevent anyone to change the design of the table in a database that contains only tables
or how to protect the database without using the programming codes
thanks in advance
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
[Non-text portions of this message have been removed]
------------------------------------
Posted by: Liz Ravenwood <Liz_Ravenwood@beaerospace.com>
------------------------------------
------------------------------------
Yahoo Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/MS_Access_Professionals/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/MS_Access_Professionals/join
(Yahoo! ID required)
<*> To change settings via email:
MS_Access_Professionals-digest@yahoogroups.com
MS_Access_Professionals-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
MS_Access_Professionals-unsubscribe@yahoogroups.com
<*> Your use of Yahoo Groups is subject to:
https://info.yahoo.com/legal/us/yahoo/utos/terms/
--------------------------------------------------------
Gary D. Schwartz Please reply to: gary.schwartz@pobox.com
Posted by: wrmosca@comcast.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (14) |
Tidak ada komentar:
Posting Komentar