Change mdw file used by databases

  • Thread starter Thread starter TC
  • Start date Start date
T

TC

I don't understand what you're asking. Is the problem that, you can't access
a database that you used to be able to access? Why do you want to change the
owner of the database?

TC
 
As part of an office 2003 rollout we want to remove the
existing shared SYSTEM.MDA If I join the default local
mdw I cant access database anymore.

DO I have to change the owner of the database to admin
with blank password? if so, how?

any help appreciated
 
thanks for your reply...

problem is we currently have some databases that use a
shared .mda file, and some dont (ie, use the default one,
with no security). I want to change so that none are
using the mda file
Click to expand...

None are using *which* mda file? The shared one, or the default one?

I suspect that you do not fully understand how workgroup files are used. If
a database has been secured against a particular mdw file, you can only use
it with >that file<. It will not work with any other workgroup file (eg. the
default file). If it >does< work with any other workgroup file, then, it was
not properly secured to begin with.

So, saying that you want a secured database to "stop using" the
corresponding workgroup file, is really saying that you want to >desecure<
that database. You can not have a secured database "stop using" its proper
workgroup file. A secured database will only work in conjunction with the
proper workgroup file.

(and then rely on file permission security).
Click to expand...

You can not use file permission security to control a user's access to the
objects in an Access database. If the database is opened in non "exclusive
read-only" mode, it will need to create an LDB file in the same folder as
the database; so the current user will need CREATE permission (or whatever
iot's called on that folder). other users who log-on to the database, will
need to update the LDB file, so they will need UPDATE permission. The last
user out of the database wil need to delete the LDB file, so he will need
DELETE permission. These actions of creating, updating & deleting the LDB
file are all performed by Access, as part of the method how Access works.

problem is that when you run the admin, and join the local
mdw then you don't have rights to open the database
anymore.
Click to expand...

*What* database? One that was secured against the local workgroup file? One
that isn't secured at all?

HTH,
TC
 
thanks for your reply...

problem is we currently have some databases that use a
shared .mda file, and some dont (ie, use the default one,
with no security). I want to change so that none are
using the mda file (and then rely on file permission
security).

problem is that when you run the admin, and join the local
mdw then you don't have rights to open the database
anymore.
 
I gather that what you want to do is remove security from these databases.
The steps are outlined in the security FAQ
You need to download and study the Security FAQ available at
http://support.microsoft.com/?kbid=207793

However, you should be aware that you can't rely on file/folder permissions
to secure a mdb.

All users need modify permission (RWXD) on the folder in order to use the
mdb in a shared environment.
 
thanks for the help, solution was to create new database,
and import all the opjects into it, understand now that
this is desecuring the database
 
Back
Top