Примери за използване на Admins group на Английски и техните преводи на Български
{-}
-
Colloquial
-
Official
-
Medicine
-
Ecclesiastic
-
Ecclesiastic
-
Computer
There must be at least one user in the Admins group at all times.
Members of the Admins group of the workgroup information file in use when the database was created.
There must be at least one user in the Admins group at all times.
Members of the Admins group of the workgroup information file in use when the database was created.
In addition, the Admin ID is also a member of the Admins group.
This is true if a user is a member of the Admins group, or if a user is the owner of an object.
Access automatically adds user accounts to the Users group when a member of the Admins group creates them.
This is true if a user is a member of the Admins group, or if a user is the owner of an object.
Access automatically adds user accounts to the Users group when a member of the Admins group creates them.
Members of the Admins group of the workgroup information file in use when the database was created.
If the target computer is joined to a domain,members of the Domain Admins group might be able to perform this procedure.
The Admins group must contain at least one user ID(there must be a database administrator), and the Admin ID is the default database administrator until you change it.
It also locks down the content so that only admins(group or network) and the owner of the document can edit the content.
The only way to remove a user account from the Users group is for a member of the Admins group to delete that user.
Administrators(members of the Admins group) can always get full permissions for objects created in the workgroup.
This account is the same forany workgroup information file, but it contains only user accounts created by members of the Admins group of that workgroup.
Administrators(members of the Admins group) can always get full permissions for objects created in the workgroup.
Consequently, unauthorized users could assume the irrevocable permissions of an administrator account(a member of the Admins group) in the workgroup defined by that workgroup information file.
One way to implement user-level security in Access 2003 orearlier versions is to change the permissions for the Users group and add new administrators to the Admins groups.
Consequently, unauthorized users could assume the irrevocable permissions of an administrator account(a member of the Admins group) in the workgroup defined by that workgroup information file.
One way to implement user-level security in Access 2003 orearlier versions is to change the permissions for the Users group and add new administrators to the Admins groups.
You can assign as many user accounts as you want to the Admins group, but only one user account can own the database- the owning account is the user account that is active when the database is created or when ownership is transferred by creating a new database and importing all of a database's objects into it.
Note: If you are using a workgroup information file created with Microsoft Access 2.0,you must be logged on as a member of the Admins group to print user and group information.
You can assign as many user accounts as you want to the Admins group, but only one user account can own the database- the owning account is the user account that is active when the database is created or when ownership is transferred by creating a new database and importing all of a database's objects into it.
Note: If you are using a workgroup information file created with Microsoft Access 2.0,you must be logged on as a member of the Admins group to print user and group information.
Because the Admin user account is exactly the same for every copy of Access, the first steps in helping to secure your database are to define administrator and owner user accounts(or use a single user account as both the administrator and owner accounts), andthen to remove the Admin user account from the Admins group.
Because the Admin user account is exactly the same for every copy of Access, the first steps in helping to secure your database are to define administrator and owner user accounts(or use a single user account as both the administrator and owner accounts), andthen to remove the Admin user account from the Admins group.
Because the Admin user account is exactly the same for every copy of Access, the first steps in helping to secure your database are to define administrator and owner user accounts(or use a single user account as both the administrator and owner accounts), andthen to remove the Admin user account from the Admins group.
For tasks like defining the group's look and description, changing privacy settings, andmanaging members and admins, click the group settings icon in the upper-right corner of the group header.
You can add an image, change the description, manage members,create additional group admins, and more.