Can't open Access file.

  • Thread starter Thread starter Luong
  • Start date Start date
L

Luong

Hello,

I have an Access database with all admins and users
permission all defined. And everything have been working
wonderfully for over a year without problem. Then just
couple days ago, when users open the database, it gave
them this message and will not let them open the DB.

"You don't have the necessary permissions to use
the 'I:\Folder\Folder\database name'object. Have your
system adminstrator or the person who created this object
establish the appropriate permissions for you."

I was able to open the database under my admins account
and check the permission info. Everything is the same,
nothing change, but what causes the users to not be able
to open the database? Is this have to do with the network
drive problem. There's no change to my database at all.

Thanks for any tips or helps.
 
It sounds as though they are no longer using the proper workgroup. Perhaps
they are using the standard system.mdw rather than the workgroup file you
provided.

Usually you provide a desktop shortcut that uses the /wrkgrp switch to point
them to the right one.

"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"
 
I have the same problem with one exception, my workgroup
file has been deleted (long story, its just gone now).
With that in mind, is there any way to open the database
so i can retrieve the info?
 
I have the same problem with one exception, my workgroup
file has been deleted (long story, its just gone now).
With that in mind, is there any way to open the database
so i can retrieve the info?

No. When you created the mdw, you would have written down the information
you used to create it (Workgroup ID, Groups/users and PIDs). With that
information you can recreate the mdw.

The only other suggestion I have is to go to a backup.
 
Hello Joan,

If the database is placed in a network drive for everyone
to access, where should I place the workgroup file I
created so other users computer can join the workgroup?
For example, do I need to place the workgroup in the same
network drive so other computers can join it? Can I create
the new workgroup to reside in my C:\Winnt\System32
folder, then create a copy of the original workgroup and
placed it in the network drive?

Which method is recommended? Thanks
 
Hi Luong,

Luong said:
Hello Joan,

If the database is placed in a network drive for everyone
to access, where should I place the workgroup file I
created so other users computer can join the workgroup?

Put the workgroup file in the same folder as the database.
Can I create
the new workgroup to reside in my C:\Winnt\System32
folder, then create a copy of the original workgroup and
placed it in the network drive?

Actually you can create your secure workgroup file anywhere (but don't name
it system.mdw and I wouldn't put it in c:\winnt\system32). Leave users
joined to their system.mdw workgroup by default, but give them a desktop
shortcut to use for the secure database.

The target would look like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"
 
Joan,

Thanks for your help. I ran into a problem trying to fix
my existing database security. A year ago, I created a
database with it assigned to a workgroup and all
permission defined for users and admins. Somehow the
workgroup file is gone and users can't access the
database. I lost all the workgroup information too.

So, I created a new workgroup for the database to join.
But I won't let me change permission etc.. even logging in
as users or admins. It looked like my existing database is
still thinking of the old (lost) workgroup. Is there a way
to completed remove the workgroup join info. from an
existing database and start over from scratch? Thanks
-----Original Message-----
Hi Luong,



Put the workgroup file in the same folder as the database.


Actually you can create your secure workgroup file anywhere (but don't name
it system.mdw and I wouldn't put it in
c:\winnt\system32). Leave users
 
Hi Luong,

Your new workgroup, is not the same as your old (unless you created it using
the exact same WID).

You say it won't let you change permissions, so that sounds like you are
able to at least open it using your new workgroup.

Since it wasn't secured properly to begin with, you may be able to:

Join the default system.mdw; create a new database, and import all the
objects from your mdb.
 
Back
Top