Access 2016-用户和权限? [英] Access 2016 - Users and permissions?

问题描述

我的雇主严格限于MS Office产品和SharePoint.我无法使用其他数据库解决方案.

My employer is strictly limited to MS Office products and SharePoint. I am unable to utilize a different database solution.

我正在尝试实现和共享一个Access数据库，以允许多个用户输入和编辑数据.但是，(当然)我想限制用户编辑数据库本身(表，表单等)的能力，并且只能通过表单查看和编辑特定数据.

I am trying to implement and share an Access database to allow multiple users to enter and edit data. However, I would (of course) like to limit the ability of users to edit the database itself (tables, forms, etc...), and only able to view and edit specific data via forms.

不幸的是，看来微软已经从较新的访问数据库中删除了用户和安全性?

Unfortunately, it appears Microsoft has removed users and security from newer access databases?

https://support.office.com/zh-CN/article/what-happened-to-user-level-security-69b362cd-503f -4e8a-a735-fb923ffb9fa3?ui = zh-CN& rs = zh-CN& ad = US

显然，我必须使用2000-2003数据库来实现安全性，但随后我将失去Access 2016的所有功能.

Apparently, I would have to use a 2000-2003 database to implement security, but then I would lose all of the features of Access 2016.

所以我的问题是，是否有一种方法可以在Access 2016数据库中实现数据库中的用户和安全性?

So my question is, is there a way to implement users and security within the database in an Access 2016 database?

推荐答案

Access中的用户安全性并非旨在防止用户修改应用程序.用户安全性旨在说出哪些用户可以打开报告或说出给定的表单.您可以使用此安全系统来防止用户干扰应用程序，但这并不是安全系统的概念或意图.

The user security in Access was NOT designed to prevent users from modify the application. The user security was designed to say what users can open a report, or say a given form. You could use this security system to ALSO prevent users from messing with the application, but that not really the concept or intent of the security system.

因此，您根本不需要(也不想)使用已久未使用的安全系统，也可以防止用户干扰您的应用程序.因此，请将这些概念分开.

So you never really did need (or want) to use the long deprecated security system as ALSO something that prevents users from messing with your application. So keep these concepts separate.

是否要锁定应用程序并防止用户混乱?好吧，首先，我们假设您的数据库已拆分.届时，您会将应用程序的已编译可执行文件"分发到每个工作站.

If you want to lock up the application and prevent users from messing around? Well, first up, we assume your database is split. At that point you will distribute a compiled "executable" of your application to each workstation.

编译后的版本意味着用户无法更改代码，表格，报告.而且，如果您的应用程序提供了某种导航"形式的表单来启动并使用给定的报表或表单，那么您的应用程序就可以隐藏您不希望用户看到的访问部分.

The compiled version means that code, forms, reports cannot be changed by users. And if your application provides some "navigation" type of form to launch + use the given report or form, then your application quite much can hide the access parts you don’t want users to see.

因此，例如，在此屏幕快照中，我提供了自定义菜单栏，用户无法看到或躲开"场景来弄乱应用程序部分.锁定应用程序的这种行为"与较旧的安全系统有关，并且不需要该安全系统，或者实际上甚至对于锁定应用程序的简单任务也建议使用该安全系统.

So for example, in this screen shot, I provided custom menu bar, and users cannot see or "go behind" the scene to mess with the application part. This "act" of locking down the application has ZERO to do with the older security system, and that security system as noted not required, or in fact even recommended for the simple task of locking down the application.

因此，请确保始终分发应用程序的编译版本(用accDE代替accDB).您对应用程序的幻想程度取决于您.上面的屏幕截图是Access 2003，但这是2010应用程序的屏幕截图–在这种情况下，我什至提供了一个自定义功能区.用户无法弄乱或看不到应用程序的任何其他部分.

So as a starting point, make sure you always distribute a compiled version of your application (an accDE in place of an accDB). How fancy you get with your application is up to you. The above screen shot was access 2003, but here is a screen cap of a 2010 application – and in this case I even provided a custom ribbon. Users cannot mess or see any other parts of the application.

用户级安全性是一个系统，允许某些用户启动特定的表单或报表，而其他用户则不启动此类表单或报表.该安全系统不是用于锁定应用程序并防止用户修改表单，报告和代码.虽然也可以使用安全系统来防止用户修改报告，但是如果您想使用户避免混乱，那么您仍然必须使用编译后的accDE，并且仍然必须花时间隐藏访问界面. (因此，安全系统在这方面确实并没有节省您的时间和精力).

User level security was a system to allow some users to launch a particular form or report, and other users to not launch such forms or reports. The security system was not for locking down the application and preventing users from modifying forms, reports and code. While the security system also could be used to prevent users from modifying reports, if you wanted to keep users out from messing around then you had to still use the compiled accDE, and you still had to spend time hiding the access interface. (so the security system really did not save you any time and effort in this regards).

这篇关于Access 2016-用户和权限?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！