Not Being Recognized as Admin

[skilche1]

About three weeks ago, my work computer crash hardcore. Windows (2000 ver) had many corrupt files in the Windows Directory and in the Registry. Because of that, IT gave me an up to date computer running Widows XP. I am still running the same version of Office (2003 Pro).

I think because I have a new machine and a different platform, I am now have issues with trying to administer the permission rights. MS Access is not recognizing me as Admin and/or Creator of the db, therefore I am not able to modify permission rights.......

Does anyone know how make this db recognize that I am the Creator of it?

Thank you in advance for your help.

Kilch

 

[Moniker]

Make sure you have administrative rights on the computer as a whole. Go to the start button, select "Run" and type gpedit.msc. That opens the Group Policy editor. Make sure you are setup as an administrator from there.

 

[skilche1]

Can you tell me where about in the Group Polocy?

Thanks a lot

 

[Moniker]

I'm at work (big company and I'm not an administrator here -- over 30,000 employees and all) so I can't pinpoint where it is, but it will be under the User folder if I remember correctly. All the users will be listed in the User folder, so click the username you're using and look at the settings. It's just exploratory from there. It's something I had to do once to enable Remote Assistance.

Also, you'll want to take that URL out of your signature. If you look at the top of this message board, there's a thing from the admins of this place asking that you don't do that.

 

[The_Doc_Man]

The problem will also include how security was implemented.

If you used workgroup security and can recover the workgroup file, then JOIN that workgroup, you should be OK.

If you used some other method of securing the DB, you might have a problem because the user ID (internally called SID) encodes not only a user number but the machine's Windows license key. New machine = new license. Which is why Workgroup Security is preferred over "rolling your own" package that reads your SID.