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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Do not have the necessary permissions

Status
Not open for further replies.

Lizard

Technical User
Mar 14, 2001
14
BE
Hi

I have been running an application working on a secure database for the
past month, but suddenly, I get an error :
You don't have the necessary permissions to use the <my database>
object. Have your system administrator or the person who created this
object establish the appropriate permissions for you. (Error 3033)

I can't open the database, eventhough I'm using the admin to connect to
the database.

I checked already that the shortcut created pointed to the right workgroup file.

This happened after a PC crash. Is it possible to bypass the security ? I badly need to recuperate all my queries and reports.

Does anyone know what can be done in a situation as such?

Thanks.

Olivier
 
Is the Database Located on your computer or the Network?
I would think that it is possible that you *.mdw file was corrupted in the crash.
Try this:
Open a new blank DB. Import the DB you are locked out of into the new one. This is how I got around a problem of converting a DB from 97 to 2000. Thanks to Gord for the info on this.

Hope this Helped,
Don
 
Don, thanks for your help, but didn't work

It gives me the same error message when using the import. To answer your first question, the database where I'm having the problem is located on a shared drive.

I still have the initial &quot;security wizard report&quot;, when I created the security the first time. I guess I will have to recreate a new workgroup file from scratch with these parameters and overwrite the &quot;corrupted&quot; one.

If anybody had the same case before, I'll be glad to hear from them.

I'm new on this site and find it better than any book or course ! Thanks to all people giving their input on all these topcs.

Olivier
 
Lizard,

Could you not get a copy of the file from the network, or get the Admin to get you a copy of it. That should solve the problem with less hassle. Of course, depending on your IT department, that could take much longer and give you as much of a headache as anything else.:) Sorry I cant be any more helpful. I am still really new to DBs, but am trying to learn as quick as possible. This is an excellent place to get answers to questions. Unfortunately with this being Good Friday, there may not be as quick of a response as usual.

Thanks,
Don
 
Don, Thanks for your advice.
I indeed simply requested a restore and hope it will work fine. It looks to be the simplest solution.

However, as I'm quite new to Access dvlpt, I'm curious to know if there's a way to re-build a workgroup file from scratch for a DB that was secured.

As far as I understood, the default system.mdw that stands in C:\programs\Microsoft Office\Office is used each time a non-secured DB is started.
During the run of the security wizard for the DB I'm securing, the startup params of that particular DB is modified in a way that the default system.mdw is &quot;replaced&quot; by the &quot;secured&quot; version for this particular *.mdb file.

As I still have the &quot;One-step Security Wizard Report&quot; document with the workgroup ID, and the description of all the secured objects, I should theoretically be able to rebuild it from scratch. BUT HOW ?

I tried to create a new workgroup file and make a &quot;join&quot; operation. But the Wrkgadm didn't ask me what DB to join with the new *.mdw file (???). Of course, I still couldn't get into my DB. I suppose that the startup parameters are &quot;hard-coded&quot; into the *.mdb file

If somebody has already rebuild a workgroup file, I would be glad to hear from his/her experience. If somebody managed to &quot;hack&quot; an Access DB for these purposes, I'm also interested :) All I want is recuperate 1 month of work.

Thanks.

Olivier
 
Hey Lizard,

I am very new to Access also. But so far from what I have learned, there is no real way to get by the security when the DB resides on a server. If you replace the *.mdw file on your computer, you just manage to lock yourself out of the DB. You would have to replace the one on the server with a mdw file that you want to use, or replace the one on your computer with the one from the server.

Please do not take this as gospel, as I said, I am new to this also. I am, however, pretty sure that that is the way it works. I wish someone with some real experience would help out with this. I would really like to know whether I am right or not.

Thanks,
Don
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top