|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
|
Thread Tools | Display Modes |
|
#11
July 19th, 2007, 06:02 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
Security logins and such
Okay, that's starting to make sense. Does the new system.mdw need to be
stored in the same folder as the DB? "Joan Wild" wrote: "Freehal04" wrote in message ... I was having the same problem Beverly was having. I created a login for Admin with a password and for some reason, the default login name was my first initial and last name and no password worked. I got the admin login to work, but it really worried me that it defaulted to my name when that was totally unexpected and unprepared for. The first time you open a secured database, it will use your Windows login name as the username for Access. Just replace that with an actual Access username. The next time you open the database it'll default to the last Access username that was used on that machine. I guess I just don't understand the worgroup administrator functions enough to be messing with it. The funny thing is, about 6 months ago, I did it with a different DB and it work fine. Every session of Access uses a workgroup file. Out of the box it uses system.mdw and silently logs you in as 'Admin'. Every system.mdw is the same, which is why/how you can freely share mdb files with other users - they too use system.mdw and are silently logged in as Admin, as user that owns everything and has full permissions to everything. When you secure a database, the first step is to create a new workgroup file. You want your secure mdb to only open when a person has the correct mdw; you don't want them to be able to open the secure mdb using system.mdw. When you create a new workgroup file, Access changes your default mdw from system.mdw to this new mdw (something always has to be set as the default). Once you have finished securing the mdb, you want to change your default back to system.mdw and use a desktop shortcut for the secure database. This way you use the shortcut to start the secure mdb. All other sessions of Access will use your default (system.mdw) which won't prompt you for a username/password. Some more reading: http://www.geocities.com/jacksonmacd...ssSecurity.pdf -- Joan Wild Microsoft Access MVP 
|
|
#12
July 19th, 2007, 06:04 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
|
Security logins and such
If you want to secure your mdb, you need to create a new workgroup file. However, since you are using 2003, may I suggest that you:
1. backup your unsecure mdb, in case you need want to start over 2. follow the steps at http://www.jmwild.com/security02.htm to secure it -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... So what is my objective, to join or create a work group? Is this work group the file that will contain all of the user names and passwords that will be using the DB? "Joan Wild" wrote: The wizard created a desktop shortcut for you to use for the secure mdb - open it via that. If you look at the properties of the shortcut you'll see that the target uses a /wrkgrp switch, which tells Access to override your default workgroup file and use the secure workgroup file for that session. -- Joan Wild Microsoft Access MVP "Beverly Weable" wrote in message ... I believe either John or Joan can help me. I set up security using the One-step Wizard and none of the logons work. I cannot get into any ACCESS database on my hard drive or the shared network, not just the one in which I created the workgroup ID and users. Any advice?
|
|
#13
July 19th, 2007, 06:14 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
|
Security logins and such
Thanks Joan, I'll give it a shot. This may take a while, I'm going to go
real slow and make sure I do it right. "Joan Wild" wrote: If you want to secure your mdb, you need to create a new workgroup file. However, since you are using 2003, may I suggest that you: 1. backup your unsecure mdb, in case you need want to start over 2. follow the steps at http://www.jmwild.com/security02.htm to secure it -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... So what is my objective, to join or create a work group? Is this work group the file that will contain all of the user names and passwords that will be using the DB? "Joan Wild" wrote: The wizard created a desktop shortcut for you to use for the secure mdb - open it via that. If you look at the properties of the shortcut you'll see that the target uses a /wrkgrp switch, which tells Access to override your default workgroup file and use the secure workgroup file for that session. -- Joan Wild Microsoft Access MVP "Beverly Weable" wrote in message ... I believe either John or Joan can help me. I set up security using the One-step Wizard and none of the logons work. I cannot get into any ACCESS database on my hard drive or the shared network, not just the one in which I created the workgroup ID and users. Any advice?
|
|
#14
July 19th, 2007, 07:01 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
|
Security logins and such
No, it doesn't - it can be stored anywhere, as long as your desktop shortcut points to the right path.
I would recommend that you keep it in the same folder as the backend on the server - it'll get backed up then, and all users can use the same file - easier to manage. -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, that's starting to make sense. Does the new system.mdw need to be stored in the same folder as the DB? "Joan Wild" wrote: "Freehal04" wrote in message ... I was having the same problem Beverly was having. I created a login for Admin with a password and for some reason, the default login name was my first initial and last name and no password worked. I got the admin login to work, but it really worried me that it defaulted to my name when that was totally unexpected and unprepared for. The first time you open a secured database, it will use your Windows login name as the username for Access. Just replace that with an actual Access username. The next time you open the database it'll default to the last Access username that was used on that machine. I guess I just don't understand the worgroup administrator functions enough to be messing with it. The funny thing is, about 6 months ago, I did it with a different DB and it work fine. Every session of Access uses a workgroup file. Out of the box it uses system.mdw and silently logs you in as 'Admin'. Every system.mdw is the same, which is why/how you can freely share mdb files with other users - they too use system.mdw and are silently logged in as Admin, as user that owns everything and has full permissions to everything. When you secure a database, the first step is to create a new workgroup file. You want your secure mdb to only open when a person has the correct mdw; you don't want them to be able to open the secure mdb using system.mdw. When you create a new workgroup file, Access changes your default mdw from system.mdw to this new mdw (something always has to be set as the default). Once you have finished securing the mdb, you want to change your default back to system.mdw and use a desktop shortcut for the secure database. This way you use the shortcut to start the secure mdb. All other sessions of Access will use your default (system.mdw) which won't prompt you for a username/password. Some more reading: http://www.geocities.com/jacksonmacd...ssSecurity.pdf -- Joan Wild Microsoft Access MVP
|
|
#15
July 19th, 2007, 07:44 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
|
Security logins and such
Okay, so I went through the entire process and I got my admin login setup,
and a got a few user logins set up. Trouble now is, when someone else tries to log on from their computer they have a straight shot to the DB without the login. I'm sure I missed something. But what? "Joan Wild" wrote: No, it doesn't - it can be stored anywhere, as long as your desktop shortcut points to the right path. I would recommend that you keep it in the same folder as the backend on the server - it'll get backed up then, and all users can use the same file - easier to manage. -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, that's starting to make sense. Does the new system.mdw need to be stored in the same folder as the DB? "Joan Wild" wrote: "Freehal04" wrote in message ... I was having the same problem Beverly was having. I created a login for Admin with a password and for some reason, the default login name was my first initial and last name and no password worked. I got the admin login to work, but it really worried me that it defaulted to my name when that was totally unexpected and unprepared for. The first time you open a secured database, it will use your Windows login name as the username for Access. Just replace that with an actual Access username. The next time you open the database it'll default to the last Access username that was used on that machine. I guess I just don't understand the worgroup administrator functions enough to be messing with it. The funny thing is, about 6 months ago, I did it with a different DB and it work fine. Every session of Access uses a workgroup file. Out of the box it uses system.mdw and silently logs you in as 'Admin'. Every system.mdw is the same, which is why/how you can freely share mdb files with other users - they too use system.mdw and are silently logged in as Admin, as user that owns everything and has full permissions to everything. When you secure a database, the first step is to create a new workgroup file. You want your secure mdb to only open when a person has the correct mdw; you don't want them to be able to open the secure mdb using system.mdw. When you create a new workgroup file, Access changes your default mdw from system.mdw to this new mdw (something always has to be set as the default). Once you have finished securing the mdb, you want to change your default back to system.mdw and use a desktop shortcut for the secure database. This way you use the shortcut to start the secure mdb. All other sessions of Access will use your default (system.mdw) which won't prompt you for a username/password. Some more reading: http://www.geocities.com/jacksonmacd...ssSecurity.pdf -- Joan Wild Microsoft Access MVP
|
|
#16
July 19th, 2007, 08:22 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
|
Security logins and such
You must have missed a step. You can't skip anything. It's a good test to see if you did it right - join the standard system.mdw and try to open the secure mdb - you shouldn't be able to even open it.
-- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, so I went through the entire process and I got my admin login setup, and a got a few user logins set up. Trouble now is, when someone else tries to log on from their computer they have a straight shot to the DB without the login. I'm sure I missed something. But what? "Joan Wild" wrote: No, it doesn't - it can be stored anywhere, as long as your desktop shortcut points to the right path. I would recommend that you keep it in the same folder as the backend on the server - it'll get backed up then, and all users can use the same file - easier to manage. -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, that's starting to make sense. Does the new system.mdw need to be stored in the same folder as the DB? "Joan Wild" wrote: "Freehal04" wrote in message ... I was having the same problem Beverly was having. I created a login for Admin with a password and for some reason, the default login name was my first initial and last name and no password worked. I got the admin login to work, but it really worried me that it defaulted to my name when that was totally unexpected and unprepared for. The first time you open a secured database, it will use your Windows login name as the username for Access. Just replace that with an actual Access username. The next time you open the database it'll default to the last Access username that was used on that machine. I guess I just don't understand the worgroup administrator functions enough to be messing with it. The funny thing is, about 6 months ago, I did it with a different DB and it work fine. Every session of Access uses a workgroup file. Out of the box it uses system.mdw and silently logs you in as 'Admin'. Every system.mdw is the same, which is why/how you can freely share mdb files with other users - they too use system.mdw and are silently logged in as Admin, as user that owns everything and has full permissions to everything. When you secure a database, the first step is to create a new workgroup file. You want your secure mdb to only open when a person has the correct mdw; you don't want them to be able to open the secure mdb using system.mdw. When you create a new workgroup file, Access changes your default mdw from system.mdw to this new mdw (something always has to be set as the default). Once you have finished securing the mdb, you want to change your default back to system.mdw and use a desktop shortcut for the secure database. This way you use the shortcut to start the secure mdb. All other sessions of Access will use your default (system.mdw) which won't prompt you for a username/password. Some more reading: http://www.geocities.com/jacksonmacd...ssSecurity.pdf -- Joan Wild Microsoft Access MVP
|
|
#17
July 19th, 2007, 08:40 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
|
Security logins and such
well I can get right to the DB even on the standard system.mdw. Should I
delete the new system.mdw and start over or what? BTW, thanks for you help with all of this. "Joan Wild" wrote: You must have missed a step. You can't skip anything. It's a good test to see if you did it right - join the standard system.mdw and try to open the secure mdb - you shouldn't be able to even open it. -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, so I went through the entire process and I got my admin login setup, and a got a few user logins set up. Trouble now is, when someone else tries to log on from their computer they have a straight shot to the DB without the login. I'm sure I missed something. But what? "Joan Wild" wrote: No, it doesn't - it can be stored anywhere, as long as your desktop shortcut points to the right path. I would recommend that you keep it in the same folder as the backend on the server - it'll get backed up then, and all users can use the same file - easier to manage. -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, that's starting to make sense. Does the new system.mdw need to be stored in the same folder as the DB? "Joan Wild" wrote: "Freehal04" wrote in message ... I was having the same problem Beverly was having. I created a login for Admin with a password and for some reason, the default login name was my first initial and last name and no password worked. I got the admin login to work, but it really worried me that it defaulted to my name when that was totally unexpected and unprepared for. The first time you open a secured database, it will use your Windows login name as the username for Access. Just replace that with an actual Access username. The next time you open the database it'll default to the last Access username that was used on that machine. I guess I just don't understand the worgroup administrator functions enough to be messing with it. The funny thing is, about 6 months ago, I did it with a different DB and it work fine. Every session of Access uses a workgroup file. Out of the box it uses system.mdw and silently logs you in as 'Admin'. Every system.mdw is the same, which is why/how you can freely share mdb files with other users - they too use system.mdw and are silently logged in as Admin, as user that owns everything and has full permissions to everything. When you secure a database, the first step is to create a new workgroup file. You want your secure mdb to only open when a person has the correct mdw; you don't want them to be able to open the secure mdb using system.mdw. When you create a new workgroup file, Access changes your default mdw from system.mdw to this new mdw (something always has to be set as the default). Once you have finished securing the mdb, you want to change your default back to system.mdw and use a desktop shortcut for the secure database. This way you use the shortcut to start the secure mdb. All other sessions of Access will use your default (system.mdw) which won't prompt you for a username/password. Some more reading: http://www.geocities.com/jacksonmacd...ssSecurity.pdf -- Joan Wild Microsoft Access MVP
|
|
#18
July 19th, 2007, 09:23 PM
posted to microsoft.public.access.gettingstarted
|
|||
|
|||
|
Security logins and such
Yes, delete the secure mdw and secure mdb; go back to your unsecure mdb, and try again.
-- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... well I can get right to the DB even on the standard system.mdw. Should I delete the new system.mdw and start over or what? BTW, thanks for you help with all of this. "Joan Wild" wrote: You must have missed a step. You can't skip anything. It's a good test to see if you did it right - join the standard system.mdw and try to open the secure mdb - you shouldn't be able to even open it. -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, so I went through the entire process and I got my admin login setup, and a got a few user logins set up. Trouble now is, when someone else tries to log on from their computer they have a straight shot to the DB without the login. I'm sure I missed something. But what? "Joan Wild" wrote: No, it doesn't - it can be stored anywhere, as long as your desktop shortcut points to the right path. I would recommend that you keep it in the same folder as the backend on the server - it'll get backed up then, and all users can use the same file - easier to manage. -- Joan Wild Microsoft Access MVP "Freehal04" wrote in message ... Okay, that's starting to make sense. Does the new system.mdw need to be stored in the same folder as the DB? "Joan Wild" wrote: "Freehal04" wrote in message ... I was having the same problem Beverly was having. I created a login for Admin with a password and for some reason, the default login name was my first initial and last name and no password worked. I got the admin login to work, but it really worried me that it defaulted to my name when that was totally unexpected and unprepared for. The first time you open a secured database, it will use your Windows login name as the username for Access. Just replace that with an actual Access username. The next time you open the database it'll default to the last Access username that was used on that machine. I guess I just don't understand the worgroup administrator functions enough to be messing with it. The funny thing is, about 6 months ago, I did it with a different DB and it work fine. Every session of Access uses a workgroup file. Out of the box it uses system.mdw and silently logs you in as 'Admin'. Every system.mdw is the same, which is why/how you can freely share mdb files with other users - they too use system.mdw and are silently logged in as Admin, as user that owns everything and has full permissions to everything. When you secure a database, the first step is to create a new workgroup file. You want your secure mdb to only open when a person has the correct mdw; you don't want them to be able to open the secure mdb using system.mdw. When you create a new workgroup file, Access changes your default mdw from system.mdw to this new mdw (something always has to be set as the default). Once you have finished securing the mdb, you want to change your default back to system.mdw and use a desktop shortcut for the secure database. This way you use the shortcut to start the secure mdb. All other sessions of Access will use your default (system.mdw) which won't prompt you for a username/password. Some more reading: http://www.geocities.com/jacksonmacd...ssSecurity.pdf -- Joan Wild Microsoft Access MVP
|
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
