Opening an accdb file with access 2003

Results 1 to 6 of 6. Thread: Solved: Open accdb in Access ? Thread Tools Show Printable Version. Solved: Open accdb in Access ?

I just got this great resource book for Access , but the problem is that the companion CD's databases are all in the new accdb format. Create a free Team What is Teams?

Collectives on Stack Overflow. Learn more. Asked 11 years, 5 months ago. Active 11 years, 5 months ago. Viewed 16k times. Improve this question. JoseK Add a comment. Active Oldest Votes. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback? That ID and those groups Admin and Users give all users full permissions on all the objects in a database — this means that any user can open, view, and change all the objects in all.

One way to implement user-level security in Access or earlier versions is to change the permissions for the Users group and add new administrators to the Admins groups. When you do so, Access automatically assigns new users to the Users group.

When you take those steps, users must log in with a password whenever they open the protected database. However, if you need to implement more specific security — allow one group of users to enter data and another to only read that data, for example — you must create additional users and groups, and grant them specific permissions to some or all of the objects in the database.

Implementing that type of user-level security can become a complex task. To help simplify the process, Access provides the User-Level Security Wizard, which makes it easier to create users and groups in a one-step process. The User-Level Security Wizard helps you to assign permissions and create user and group accounts.

User accounts contain user names and unique personal ID numbers PIDs needed to manage a user's permissions to view, use, or change database objects in an Access workgroup. Group accounts are a collection of user accounts that, in turn, reside in a workgroup. Access uses a group name and PID to identify each work group, and the permissions assigned to a group apply to all users in the group.

For more information about using the wizard, see Set user-level security , later in this article. After you complete the wizard, you can manually assign, modify, or remove permissions for user and group accounts in your workgroup for a database and its existing tables, queries, forms, reports, and macros. You can also set the default permissions that Access assigns for any new tables, queries, forms, reports, and macros that you or another user add to a database.

In Access and earlier versions, a workgroup is a group of users in a multiuser environment who share data. A workgroup information file contains the user and group accounts, passwords, and permissions set for each individual user or group of users. When you open a database, Access reads the data in the workgroup information file and enforces the security settings that the file contains.

In turn, a user account is a combination of user name and personal ID PID that Access creates to manage the user's permissions. Permissions assigned to a group apply to all users in the group. Those security accounts can then be assigned permissions for databases and their tables, queries, forms, reports, and macros. The permissions themselves are stored in the security-enabled database.

The first time a user runs Access or earlier versions, Access automatically creates an Access workgroup information file that is identified by the name and organization information that the user specifies when he installs Access. For Access , the setup program adds the relative location of this workgroup information file to the following registry keys:.

Because this information is often easy to determine, it is possible for unauthorized users to create another version of this workgroup information file.

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. To prevent unauthorized users from assuming these permissions, create a new workgroup information file, and specify a workgroup ID WID , a case-sensitive alphanumeric string from 4 to 20 characters long that you enter when you create a new workgroup information file.

Creating a new workgroup uniquely identifies the Admin group for this workgroup file. Only someone who knows the WID will be able to create a copy of the workgroup information file.

To create the new file, you use the User-Level Security Wizard. Important: Be sure to write down your exact name, organization, and workgroup ID — including whether letters are uppercase or lowercase for all three entries — and keep them in a secure place. If you must re-create the workgroup information file, you must supply the exact same name, organization, and workgroup ID.

If you forget or lose these entries, you might lose access to your databases. User-level security recognizes two types of permissions: explicit and implicit. Explicit permissions are those permissions that are granted directly to a user account; no other users are affected. Implicit permissions are the permissions granted to a group account. Adding a user to that group grants the group's permissions to that user; removing a user from the group takes away the group's permissions from that user.

When a user attempts to perform an operation on a database object that employs security features, that user's set of permissions are based on the intersection of that user's explicit and implicit permissions.

A user's security level is always the least restrictive of that user's explicit permissions and the permissions of any and all groups to which that user belongs. For this reason, the least complicated way to administer a workgroup is to create new groups and assign permissions to the groups, rather than to individual users. Then you can change individual users' permissions by adding or removing those users from groups.