Re: Problem while opeing the Access DB

From: Joan Wild (jwild_at_nospamtyenet.com)
Date: 07/27/04 

Date: Tue, 27 Jul 2004 10:09:39 -0400

You are getting that message because the database was secured in 97.

You can provide the 97 workgroup file, and they can use it in 2000, however
as the message states the users would need modify design/administer
permissions or be the owner of the mdb. As this isn't likely, they won't
get very far.

I would suggest you unsecure it using 97, convert it to 2000 and resecure,
and provide them with a 2000 version. 

-- 
Joan Wild
Microsoft Access MVP
Anil Kumar A A wrote:
> I have a access Database created in NT (office 97), but my clients
> have migrated to W2k (office 2K) so when they try to open the Access
> MDB which was created in NT...it throws the below given error....
>
> The current user account doesn't have permission to convert or enable
> this database.
>
> To convert or enable a database, ensure the following:
> * You must join the workgroup that defines the user accounts used to
> access the database.
> * Your user account must have Open/Run and Open Exclusive permissions
> for the database object.
> * Your user account must have Modify Design or Administer permissions
> for all the tables in the database, or it must be the owner of all
> tables in the database.
> * Your user account must have Read Design permission for all objects
> in the database.
> * Request that other users close the database.
>
> How do i over come this..plz help me out..as i am running short of
> ideas to resolve this problem..
>
> Appreciate u'r effort in helping me out....
>
> Thanks in advance

Relevant Pages

  • Re: Change User ID - Possible?
    ... Never directly change SharePoint data in the database. ... The Only way you can do is to replace the user account i.e. delete the old user account and add a new user account, but before you delete the old account you have to find out the permissions of the old account and apply the same permissions to the new account, this can be automated through code. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Problem while opeing the Access DB
    ... You would join the 97 workgroup file; open Access 2000, ... group, or as the owner of the mdb, and should be able to convert it. ... >> You are getting that message because the database was secured in 97. ... >>> * Your user account must have Open/Run and Open Exclusive ...
    (microsoft.public.access.security)
  • Re: Trying to program workgroup security using DAO... Help!!
    ... After you created a new workgroup file, you then created a new user to be a member of Admins. ... Here are the steps I've taken to secure a target database (which is ... Assigning permissions. ... Assigned all specific permissions to objects for the new groups I ...
    (microsoft.public.access.security)
  • Re: Becoming the Owner
    ... so you can open the database while joined to ... and check the permissions for the Database object type. ... remove the permissions on all objects for the Users group. ... workgroup file. ...
    (microsoft.public.access.security)
  • Re: Sorting out security
    ... Right now I am set up with a functional clean database, ... The default "admin" user is not the owner of any part of the ... database and has no permissions whatsoever. ... > The location of the current workgroup file is recorded in the ...
    (microsoft.public.access.security)
Quantcast