Re: permissions to import after a new workgroup file?
- From: "Chris Mills" <phad_nospam@xxxxxxxxxxxxxx>
- Date: Mon, 19 Sep 2005 17:12:49 +1200
To import as a new owner from a previous owner, obviously you need permissions
for the objects in the original database. As you setup the original security,
there should be no problems knowing what groups, users, or passwords or PIDs
you setup.
Normally permissions are assigned via Groups. I'd think you would create a
temporary Group consistent with your previous scheme, or one easy way to
describe is to temporarily assign permissions to the Users Group (in the old
database, and which all mdw's have). Anyway, you do need to give the new owner
permissions to the old database, perhaps temporarily for the old database by
some means, in order to import. (otherwise it would hardly have been secure!)
You shouldn't be altering security measures with the "default workgroup". As
soon as you decided to implement security, you should be always using a
"specific workgroup". This could be a COPY of another workgroup file (for all
I know). Also, remember that the workgroup stores Users and Groups, but the
MDB stores all the object permissions. There must be some level of match
between them (namely the mdb must store some cryptic of the User and Group
details).
(it doesn't really matter if you mess-up the Access default system.mdw. That
can be recovered from nearly anywhere, say CD or another installation)
> Did I do this backwards?
I don't think so. You may be doing things a different way from the Security
FAQ, or the Security Wizard, but I think that's good if it helps you
understand it. If anyone could just create a new owner and import, then what
would be the point? Your old security seems to be working fine!
Chris
"miky" <mikynog@xxxxxxxxx> wrote in message
news:1126999431.511179.32930@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi,
> I developed a database with security in mind but assumed that it would
> be ok to implement at the end of development. I'm trying to import the
> objects to a new database using a new mdw but it's telling me that I
> don't have the permissions to do this. Did I do this backwards? I
> don't want to apply the security measures on the default workgroup
> file, obviously.
>
> The message I'm getting is: "You do not have the necessary permissions
> to use the [mdb object]. Have your system administrator or the person
> who created this object establish the appropriate permissions for you."
>
> There may be a possibility that the default system.mdw file was changed
> in some way that maybe causes this not to work anymore. I had added an
> additional user of the admins group when I was testing out the security
> model. Could this have anything to do with this? I've tried putting
> the users and groups back to the way it was in the beginning but it
> doesn't work.
>
> I'd just like to be able to import all the objects to a new database
> using a new mdw. I think this would fix things but it's not behaving
> the way I'd hoped.
>
> Your help on this is greatly appreciated. Thanks,
>
> miky
>
.
- Follow-Ups:
- References:
- Prev by Date: Re: Validate.
- Next by Date: Access security explanation and explorer tool available
- Previous by thread: permissions to import after a new workgroup file?
- Next by thread: Re: permissions to import after a new workgroup file?
- Index(es):
Relevant Pages
|
