Results 1 to 5 of 5
  1. #1
    Join Date
    Aug 2009

    Unanswered: You do not have the necessary permissions to use the <name> object - Problem

    Greetings all,

    I am Active Duty in the United States Air Force stationed in California. Recently our communications guys transfered all of our data from one server to another following that transfer there was a problem with a very important Access file I use.

    Now I am pretty good at hardware, decent at most software and a complete idiot with Access. I have done my homework prior to posting though.

    I've learned the error I'm getting "You do not have the necessary permissions to use the <name> object. Have your system administrator or the person who created this object establish the appropriate permissions for you. (Error 3033)" comes up because the Database I am trying to open is secured and apparently I don't have the proper Secure workgroup file.

    I realize the easiest fix would be to have the file's owner open the file and correct the problem but being in the Military he is no longer at this base. The second easiest fix would be to use the unsecured .bak file. The .bak file is no-where to be found.

    The good news is I was able to find the One-step Security Wizard Report that has the WID.

    The db was made in Access 2000 and I currently have Access 2007.

    How can I re-create the workgroup file and give myself access?

    Thank you very much in advance,

    Nick Bishop, SSgt USAF

  2. #2
    Join Date
    Nov 2007
    Adelaide, South Australia
    Upgrade the file to 2007? 2007 doesn't support user level security and upgraded files simply have their security stripped.

    Not sure if you'll need the security restored before you can do it though.

    Otherwise you have to find the correct MDW file that contains the security information.

    Did the person who made it leave some documentation?
    Owner and Manager of
    CypherBYTE, Microsoft Access Development Specialists.
    Microsoft Access MCP.
    And all around nice guy!

    "Heck it's something understood by accountants ... so it can't be 'that' difficult..." -- Healdem
    "...teach a man to code and he'll be frustrated for life! " -- georgev

  3. #3
    Join Date
    Oct 2004
    Melbourne, Australia

    Access Permissions and the WorkGroups File

    If you cannot find a workgroups (.mdw) file, then there may be a System.mdw stored either in the Program Files area or the Application Data. It may be that, in the absence, of a specified workgroups file, Access reverts to this default workgroups file. Typically, this file contains a user called "admin" as a default. This is a misnomer as this is not a real administrator at all (though it could be made one).

    You could test this hypothesis by creating a new (empty) database with System.mdw as it's workgroups file (look for the Workgroups Administrator option in Tools/Security and apply to "join" the workgroup. After that, you can install other users and groups, mirroring the users and groups in your original database. Then you open the original database with a command line which includes the /wkgrps switch, specifying the new workgroup file.

    At the next level, if you want ot make specific objects (tables, forms, etc.) accessible to specific users, you must go to the User/Groups Permissions utility in the same menu. Remember however that these permissions are attributes of the database and not of the workgroups file.
    Last edited by Jim Wright; 08-20-09 at 02:44.

  4. #4
    Join Date
    Aug 2009

    .mdw file

    So apparently its the .mdw that is the problem. Double sided question. I understand that I can recreate the .mdw using the One-step Security Wizard Report. When that .mdw is made does it need to be 100% accurate to the origonal or can it have an additonal user added in? The reason I ask is because the two file creators in the origional .mdw are no longer at this base. I have tried making the file but it is not working for me. Would someone be willing to try creating one for me? I am willing to provide a copy of the One-step Security Wizard report.

    Thank you all again for your help.

  5. #5
    Join Date
    Apr 2004
    metro Detroit
    Nick, first and foremost - Thanks for your service.

    If the database was secured, you will need the mdw file to have the same name and ID. Were you using a shortcut with a command line switch to open the database or opening the mdb file directly?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts