|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Database RuinedOk,
So I try to set up security. I cannot access / update any tables. If I try to assign Admin to to update it says Admin does not have permissions. I have tried deleteing / recreating / deleting / recreating workgroup files but I cannot change anything. My backup databses - cant change anything with them either. Can anyone advise how to turn securuit OFF like it never existed in the first place? Hello GLT.
"GLT" wrote: So the user account you use to log on when starting Access has not> Ok, > > So I try to set up security. > > I cannot access / update any tables. the permissions to access/update the tables. > If I try to assign Admin to to update it says Admin does not have In a properly secured database, only the owner of that database has> permissions. the "manage" permission whichs allows him to assign permissions. > I have tried deleteing / recreating / deleting / recreating You have to re-create theworkgroup file correctly. As you have done> workgroup files but I cannot change anything. this several times, you must have seen the dialog box displaying a summary of the workgroup's settings, stating that this will be the last time you can view these VERY important settings. You have to use the exact same settings when recreating the workgroup. > My backup databses - cant change anything with them either. How about a backup of the unsecured version of the database?> Can anyone advise how to turn securuit OFF like it never existed To "remove" security you will have to assign all permissions to the> in the first place? users group. To be able to do this, you will have to log on as a user that has the permissions to do so: The one who created the database. If this should be the Admin user of the workgroup (it shouldn't be him, because that's less secure), you will simply have to re-create the workgroup and restart Access as the admin of that workgroup. If the owner of the database is a special user of that workgroup, you will also (in addition to re-creating the workgroup) have to re-create that user. To do so, you will have to create a user with the proper user name and PID (personal identifier). You see that this PID has a similar importance as the workgroup data, because the PID is shown only when creating the user and cannot be accessed later. Unfortnaltely, there is no hint about the importance to keep that information in a secure location. If you should be able to re-create that user, remember to assign a password to the admin user in order to be able to log on as the owner of the database (with still a blank password) when re-starting Access and hopefully accessing the database successfully now. Remark: Obviously you can access the database but you can't update data or security settings. This is either bad (insecure configuration) or good (you have successfully re-created the workgroup but are logging in as Admin with a blank password, which my be the desired behaviour of all clents to connect to your database). If the workgroup already contains the owner of that database, try to temporarily assign a password to the admin and log on as the owner of the database. (Or create a shortcut on your desktop using the /user switch.) -- Regards, Wolfgang Hi Wolfgang,
Thanks for your response. I recovered my DB from one of our system backups so at least four weeks of work is not wasted. I had no idea setting up security could cause so many problems. The problem I think was that the DB had all objects as unkown. When I was using the user level security wizard it kept crashing (it normally prints out a report on the PID's etc - for this reason I did not write any of it down). I will try attempt # 2 with security this afternoon, and hopefully will come out with a secure DB - not a lemon DB :) Cheers Show quote "Wolfgang Kais" wrote: > Hello GLT. > > "GLT" wrote: > > Ok, > > > > So I try to set up security. > > > > I cannot access / update any tables. > > So the user account you use to log on when starting Access has not > the permissions to access/update the tables. > > > If I try to assign Admin to to update it says Admin does not have > > permissions. > > In a properly secured database, only the owner of that database has > the "manage" permission whichs allows him to assign permissions. > > > I have tried deleteing / recreating / deleting / recreating > > workgroup files but I cannot change anything. > > You have to re-create theworkgroup file correctly. As you have done > this several times, you must have seen the dialog box displaying a > summary of the workgroup's settings, stating that this will be the > last time you can view these VERY important settings. You have to > use the exact same settings when recreating the workgroup. > > > My backup databses - cant change anything with them either. > > How about a backup of the unsecured version of the database? > > > Can anyone advise how to turn securuit OFF like it never existed > > in the first place? > > To "remove" security you will have to assign all permissions to the > users group. To be able to do this, you will have to log on as a user > that has the permissions to do so: The one who created the database. > If this should be the Admin user of the workgroup (it shouldn't be > him, because that's less secure), you will simply have to re-create > the workgroup and restart Access as the admin of that workgroup. > If the owner of the database is a special user of that workgroup, > you will also (in addition to re-creating the workgroup) have to > re-create that user. To do so, you will have to create a user with > the proper user name and PID (personal identifier). You see that this > PID has a similar importance as the workgroup data, because the PID > is shown only when creating the user and cannot be accessed later. > Unfortnaltely, there is no hint about the importance to keep that > information in a secure location. > If you should be able to re-create that user, remember to assign a > password to the admin user in order to be able to log on as the > owner of the database (with still a blank password) when re-starting > Access and hopefully accessing the database successfully now. > > Remark: > Obviously you can access the database but you can't update data or > security settings. This is either bad (insecure configuration) or > good (you have successfully re-created the workgroup but are logging > in as Admin with a blank password, which my be the desired behaviour > of all clents to connect to your database). If the workgroup already > contains the owner of that database, try to temporarily assign a > password to the admin and log on as the owner of the database. > (Or create a shortcut on your desktop using the /user switch.) > > -- > Regards, > Wolfgang > > > On Thu, 15 Nov 2007 16:56:02 -0800, GLT
<G**@discussions.microsoft.com> wrote: It is unfortunate the MSFT documentation is not more clear about this: workgroup security is an advanced topic, and you should download, study, and fully understand the MSFT security FAQ from microsoft.com before starting this project. -Tom. Show quote >Hi Wolfgang, > >Thanks for your response. > >I recovered my DB from one of our system backups so at least four weeks of >work is not wasted. I had no idea setting up security could cause so many >problems. > >The problem I think was that the DB had all objects as unkown. When I was >using the user level security wizard it kept crashing (it normally prints out >a report on the PID's etc - for this reason I did not write any of it down). > >I will try attempt # 2 with security this afternoon, and hopefully will come >out with a secure DB - not a lemon DB :) > >Cheers > >"Wolfgang Kais" wrote: > >> Hello GLT. >> >> "GLT" wrote: >> > Ok, >> > >> > So I try to set up security. >> > >> > I cannot access / update any tables. >> >> So the user account you use to log on when starting Access has not >> the permissions to access/update the tables. >> >> > If I try to assign Admin to to update it says Admin does not have >> > permissions. >> >> In a properly secured database, only the owner of that database has >> the "manage" permission whichs allows him to assign permissions. >> >> > I have tried deleteing / recreating / deleting / recreating >> > workgroup files but I cannot change anything. >> >> You have to re-create theworkgroup file correctly. As you have done >> this several times, you must have seen the dialog box displaying a >> summary of the workgroup's settings, stating that this will be the >> last time you can view these VERY important settings. You have to >> use the exact same settings when recreating the workgroup. >> >> > My backup databses - cant change anything with them either. >> >> How about a backup of the unsecured version of the database? >> >> > Can anyone advise how to turn securuit OFF like it never existed >> > in the first place? >> >> To "remove" security you will have to assign all permissions to the >> users group. To be able to do this, you will have to log on as a user >> that has the permissions to do so: The one who created the database. >> If this should be the Admin user of the workgroup (it shouldn't be >> him, because that's less secure), you will simply have to re-create >> the workgroup and restart Access as the admin of that workgroup. >> If the owner of the database is a special user of that workgroup, >> you will also (in addition to re-creating the workgroup) have to >> re-create that user. To do so, you will have to create a user with >> the proper user name and PID (personal identifier). You see that this >> PID has a similar importance as the workgroup data, because the PID >> is shown only when creating the user and cannot be accessed later. >> Unfortnaltely, there is no hint about the importance to keep that >> information in a secure location. >> If you should be able to re-create that user, remember to assign a >> password to the admin user in order to be able to log on as the >> owner of the database (with still a blank password) when re-starting >> Access and hopefully accessing the database successfully now. >> >> Remark: >> Obviously you can access the database but you can't update data or >> security settings. This is either bad (insecure configuration) or >> good (you have successfully re-created the workgroup but are logging >> in as Admin with a blank password, which my be the desired behaviour >> of all clents to connect to your database). If the workgroup already >> contains the owner of that database, try to temporarily assign a >> password to the admin and log on as the owner of the database. >> (Or create a shortcut on your desktop using the /user switch.) >> >> -- >> Regards, >> Wolfgang >> >> >> "GLT" <G**@discussions.microsoft.com> wrote in message With respect, correctly setting up ULS causes no problems. People sometimes news:A841CA89-65A0-45C4-BA88-77D01DD43548@microsoft.com... > Hi Wolfgang, > > Thanks for your response. > > I recovered my DB from one of our system backups so at least four weeks of > work is not wasted. I had no idea setting up security could cause so many > problems. dive in thinking that it is a doddle when it is not, and the problem with using the wizard is that it does stuff without telling you so you gain no appreciation of what's going on. > In addition to Tom's advice, have a look at the example on my web site. > The problem I think was that the DB had all objects as unkown. When I was > using the user level security wizard it kept crashing (it normally prints > out > a report on the PID's etc - for this reason I did not write any of it > down). > > I will try attempt # 2 with security this afternoon, and hopefully will > come > out with a secure DB - not a lemon DB :) > Google and search this group for Joan Wild too. Regards, Keith. www.keithwilby.com Keith Wilby wrote:
Show quote > "GLT" <G**@discussions.microsoft.com> wrote in message As I have stated before...There are two areas of Access development (Security > news:A841CA89-65A0-45C4-BA88-77D01DD43548@microsoft.com... > > Hi Wolfgang, > > > > Thanks for your response. > > > > I recovered my DB from one of our system backups so at least four > > weeks of work is not wasted. I had no idea setting up security > > could cause so many problems. > > With respect, correctly setting up ULS causes no problems. People > sometimes dive in thinking that it is a doddle when it is not, and > the problem with using the wizard is that it does stuff without > telling you so you gain no appreciation of what's going on. and Replication) that in my opinion fall into the category "If you have to ask questions about it, you are not qualified to be be using it (yet)". -- Rick Brandt, Microsoft Access MVP Email (as appropriate) to... RBrandt at Hunter dot com "Keith Wilby" <h***@there.com> wrote in message news:473d50a8$1_1@glkas0286.greenlnk.net... I've never heard the word doddle before; sent me to dictionary.com.> "GLT" <G**@discussions.microsoft.com> wrote in message > news:A841CA89-65A0-45C4-BA88-77D01DD43548@microsoft.com... > > With respect, correctly setting up ULS causes no problems. People sometimes > dive in thinking that it is a doddle Learn something new every day. -- Joan Wild Microsoft Access MVP Show quote
"Joan Wild" <jwild@nospamtyenet.com> wrote in message This is indeed a first, Joan ;-)news:uA3KFYGKIHA.1204@TK2MSFTNGP03.phx.gbl... "Keith Wilby" <h***@there.com> wrote in message news:473d50a8$1_1@glkas0286.greenlnk.net... >> "GLT" <G**@discussions.microsoft.com> wrote in message >> news:A841CA89-65A0-45C4-BA88-77D01DD43548@microsoft.com... >> >> With respect, correctly setting up ULS causes no problems. People >> sometimes >> dive in thinking that it is a doddle > I've never heard the word doddle before; sent me to dictionary.com. > Learn something new every day. More and more UK-isms seem to be finding their way across the pond. I heard the word "loo" in a US sitcom recently. Keith.  |
|||||||||||||||||||||||
Other interesting topics