Carrying this thread even further, by using SQL Server databases you can completely protect tables from design changes. You can also grant separate read/write/edit/delete permissions at the column (field) level.
---In MS_Access_Professionals@yahoogroups.com, <strive4peace2008@yahoo.com> wrote :
hi youssef,
sabah al khair,as it probably is for you if you read this anytime soon. I agree with Graham that ULS was a good idea, but alas, it is gone ... so, Bill's tool is even more essential for every Access developer, in my opinion. Locking down the Access application, as best you can with what is built-in, is step 1.
Beyond that ... even though there are ways around it, limiting being able to see files by preventing that with network scan permissions when browsing is another idea -- as is changing the file extension so it is something other than ACCDB -- so casual users won't even realize it is an Access database ;)
Another way to mask things is using pass-thru queries instead of linking to tables.
programming codes"> "or how to protect the database without using the
you're kidding, right? ( ... saying with a smile because ... if you are to be serious about Access, you must learn some VBA ... no way around that. The good news is that it is easy for any logical mind to learn:
Learn VBA
http://www.AccessMVP.com/strive4peace/VBA.htm
with a bit of VBA under your belt, you can also encode/decode specific data -- well that doesn't protect design changes ... but I'm kinda with Liz on this one, if someone is exploring around so much, maybe their skills would be better doing something else.� Maybe you can log who uses those files another way using your network tools.
with network permissions, you may be able to prevent copying files, depending on your system, which also hinders analysis. You can create VBA that runs and if a certain switch is not used to get in, Access closes. Code again. If you learn the basics of VBA, then you can target what you need to do and supplement your understanding as needed.
crystal
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
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
------------------------------------
Posted by: wrmosca@comcast.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (15) |
Tidak ada komentar:
Posting Komentar