|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
User level security 2002 / 2003I've got an XP2002 db that I secured via user level security. My
problem is that my XP2003 users cannot open forms. They get the error "you do not have open/run priveleges on form" I've had those same 2003 users log into the db on a 2002 machine and they are able to open the forms. Is there a file format issue here? Any ideas? .mdw compatibility issues? Cfox4 wrote:
> I've got an XP2002 db that I secured via user level security. My Are they using your secured workgroup (MDW) file? If not, then your actual > problem is that my XP2003 users cannot open forms. They get the error > "you do not have open/run priveleges on form" > > I've had those same 2003 users log into the db on a 2002 machine and > they are able to open the forms. Is there a file format issue here? > Any ideas? .mdw compatibility issues? problem is that you didn't apply security properly in the first place. Usually this would result in no security at all, but in your case the security "hole" is only letting then into the file, but is at least stopping them at the forms. One of the more common mistakes when applying security is leaving "Admin" as the owner of the database and some or all of the objects. As owner Admin will be allowed in even though he has no "permissions". Any objects that you created after securing the file would not be owned by Admin so someone opening the file with the wrong workgroup would not be able to use those objects. You should start over with your security until you achieve the proper behavior which is that someone using the wrong workgroup is not able to open the file at all. Then you can give all users a shortcut for your file that specifies the correct workgroup as a command line argument. Using that shortcut they would be prompted to log in and should be granted the permissions assigned to the account they use. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com Thanks for the response. Yes they are using the same workgroup file. I've
even changed the owner of my start up form to be the group that these guys belong to. I've made shortcuts for both Access2002 and 2003 since 2002's access.exe is in office10 and 2003 in office11. Both shortcuts use the same /wrkgrp switch and path is exactly the same to the wrkgrp. The original unsecured db was in 2000 file format and I notice that the mdw is also 2000 format. I wouldn't think this would be an issue but it's possible I guess. The thing I find interesting is that the any user who has Access 2003 installed on their machine can go to a machine with Access 2002 on it and log in successfully. This would indicate that the issue is related to 2003. Any other thoughts or suggestions??? Thanks Show quoteHide quote "Rick Brandt" wrote: > Cfox4 wrote: > > I've got an XP2002 db that I secured via user level security. My > > problem is that my XP2003 users cannot open forms. They get the error > > "you do not have open/run priveleges on form" > > > > I've had those same 2003 users log into the db on a 2002 machine and > > they are able to open the forms. Is there a file format issue here? > > Any ideas? .mdw compatibility issues? > > Are they using your secured workgroup (MDW) file? If not, then your actual > problem is that you didn't apply security properly in the first place. Usually > this would result in no security at all, but in your case the security "hole" is > only letting then into the file, but is at least stopping them at the forms. > > One of the more common mistakes when applying security is leaving "Admin" as the > owner of the database and some or all of the objects. As owner Admin will be > allowed in even though he has no "permissions". Any objects that you created > after securing the file would not be owned by Admin so someone opening the file > with the wrong workgroup would not be able to use those objects. > > You should start over with your security until you achieve the proper behavior > which is that someone using the wrong workgroup is not able to open the file at > all. Then you can give all users a shortcut for your file that specifies the > correct workgroup as a command line argument. Using that shortcut they would be > prompted to log in and should be granted the permissions assigned to the account > they use. > > -- > Rick Brandt, Microsoft Access MVP > Email (as appropriate) to... > RBrandt at Hunter dot com > > > Cfox4 wrote:
Show quoteHide quote > Thanks for the response. Yes they are using the same workgroup You could try converting your MDW to 2002/2003 format (a separate copy of > file. I've even changed the owner of my start up form to be the > group that these guys belong to. > > I've made shortcuts for both Access2002 and 2003 since 2002's > access.exe is in office10 and 2003 in office11. Both shortcuts use > the same /wrkgrp switch and path is exactly the same to the wrkgrp. > > The original unsecured db was in 2000 file format and I notice that > the mdw is also 2000 format. I wouldn't think this would be an issue > but it's possible I guess. > > The thing I find interesting is that the any user who has Access 2003 > installed on their machine can go to a machine with Access 2002 on it > and log in successfully. > > This would indicate that the issue is related to 2003. Any other > thoughts or suggestions??? Thanks course) and then see if the users with 2003 can use that. -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com
How Do I Prevent Access 2003 Crash when using Digital ID & Library
Unsecuring a secure Access Database? Permissions Help Design Master security Providing logins for users and filtering records based on users Backend DB Password digital signature trouble Is there a way to set up an audit tracking in Access? access security Allowing only certain users to view design and code |
|||||||||||||||||||||||