Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What is .mdw?
- Thread starter ktchan741
- Start date
The .mdw is the workgroup file.
When you start an Access application you belong to a workgroup. By default this is the 'System' workgroup and is controlled by the system.mdw file.
The workgroup file is used in Access security to record usernames and user passwords and controls access(small a) to the applications which are part of this designated workgroup.
If you implement full Access security then part of the process is to create a workgroup file which will hold details of the users and passwords.
Access security is a heavy matter and there is a Security Faq onthe MS support site.
When you start an Access application you belong to a workgroup. By default this is the 'System' workgroup and is controlled by the system.mdw file.
The workgroup file is used in Access security to record usernames and user passwords and controls access(small a) to the applications which are part of this designated workgroup.
If you implement full Access security then part of the process is to create a workgroup file which will hold details of the users and passwords.
Access security is a heavy matter and there is a Security Faq onthe MS support site.
- Thread starter
- #3
lupins, thanks for the advise. How can the .mdw file be created then? Does the .mdw file point to the .mdb file?
I have an access application that is executed from a short-cut. It runs fine on the laptop. However, when the it is loaded onto the PC, the short-cut no longer work. I change the target location where the mdw file is residing but it still prompt me that "mdw file is required for start-up". Can you advise?
I have an access application that is executed from a short-cut. It runs fine on the laptop. However, when the it is loaded onto the PC, the short-cut no longer work. I change the target location where the mdw file is residing but it still prompt me that "mdw file is required for start-up". Can you advise?
to secure your access file using .mdw, go to the Tools menu and click the "Security" > user-level security wizard. From there, there'll be some guidelines to help you with... just follow the instructions.
Everytime you want to open you access file to another PC, be sure you copy the exact file (i.e. personal.mdb) with the security file (e.q. personal.mdw) into the PC. After that you have to redirect your access file to the location of the .mdw file (tools>security>Security administrator> join)
You should however,read the MS faq at least to help you setup your security. If its only for a single user ust use "Set database password" also located in the "Tools>security" menu.
Everytime you want to open you access file to another PC, be sure you copy the exact file (i.e. personal.mdb) with the security file (e.q. personal.mdw) into the PC. After that you have to redirect your access file to the location of the .mdw file (tools>security>Security administrator> join)
You should however,read the MS faq at least to help you setup your security. If its only for a single user ust use "Set database password" also located in the "Tools>security" menu.
If the application on the laptop is using a .mdw file then the same .mdw file must be copied to the pc along with the mdw file. The location of the.mdb and .mdw files on a machine doesn't matter as long as the shortcut points to the correct location.
The .mdw file is created using the workgroup administration program which is installed as part of Access. It is not possible to recreate a .mdw file without the information that was used to create it originally. The procedure for creating a .mdw file tells you to print this data as part of the process.
The .mdw does not point to any database (but any specific database using full Access security will require a specific workgroup file to be used). In general terms, it controls access to all databases created while the user(developer) was joined to (was a member of) that specific workgroup. In operation, you might imagine a small department with several Access applications. The ability of any individual to login to any of them is controlled by the workgroup file.
Individual databases use the usergroup and user names and identity codes (not passwords) that were used to set up the workgroup file to record which user/group has what permissions in that database.
When Access is installed a default workgroup of 'System' is used and a system.mdw file is created. When you first implement full security on a database, it is advisable to create a workgroup file with a different and meaningful name because every Access installation has a system.mdw file and this would lead to confusion as to the correct workgroup file to be used.
The .mdw file is created using the workgroup administration program which is installed as part of Access. It is not possible to recreate a .mdw file without the information that was used to create it originally. The procedure for creating a .mdw file tells you to print this data as part of the process.
The .mdw does not point to any database (but any specific database using full Access security will require a specific workgroup file to be used). In general terms, it controls access to all databases created while the user(developer) was joined to (was a member of) that specific workgroup. In operation, you might imagine a small department with several Access applications. The ability of any individual to login to any of them is controlled by the workgroup file.
Individual databases use the usergroup and user names and identity codes (not passwords) that were used to set up the workgroup file to record which user/group has what permissions in that database.
When Access is installed a default workgroup of 'System' is used and a system.mdw file is created. When you first implement full security on a database, it is advisable to create a workgroup file with a different and meaningful name because every Access installation has a system.mdw file and this would lead to confusion as to the correct workgroup file to be used.
- Status
Similar threads
