I'm trying to import objects from db#1 (secured) into a blank db#2
(unsecured). I believe if I use the Workgroup Adminstrator to join db#1's
mdw, I should be able to import from within db#2. I would prefer not to
export from db#1 to db#2 because I can only export one object at a time.

Once I've copied the objects, how would I go about copying the exact
security settings from db#1 onto db#2? I'm troubleshooting corruption.
That's why I'm moving to a blank database.

I would appreciate your help. Thx.

"REC" <(E-Mail Removed)> wrote in message
newsFEA4230-D445-4E61-AC6D-(E-Mail Removed)...
> I'm trying to import objects from db#1 (secured) into a blank db#2
> (unsecured). I believe if I use the Workgroup Adminstrator to join db#1's
> mdw, I should be able to import from within db#2. I would prefer not to
> export from db#1 to db#2 because I can only export one object at a time.
>
> Once I've copied the objects, how would I go about copying the exact
> security settings from db#1 onto db#2? I'm troubleshooting corruption.
> That's why I'm moving to a blank database.
>
> I would appreciate your help. Thx.

You need to join db#1's security group before you open db#2. You will then
be able to assign permissions - permissions are not inherited on imported
objects.

Regards,
Keith.
www.keithwilby.com

Thanks and DOH! Do you know of any utilities that can copy the security
settings? thx.

"Keith" wrote:

> "REC" <(E-Mail Removed)> wrote in message
> newsFEA4230-D445-4E61-AC6D-(E-Mail Removed)...
> > I'm trying to import objects from db#1 (secured) into a blank db#2
> > (unsecured). I believe if I use the Workgroup Adminstrator to join db#1's
> > mdw, I should be able to import from within db#2. I would prefer not to
> > export from db#1 to db#2 because I can only export one object at a time.
> >
> > Once I've copied the objects, how would I go about copying the exact
> > security settings from db#1 onto db#2? I'm troubleshooting corruption.
> > That's why I'm moving to a blank database.
> >
> > I would appreciate your help. Thx.
>
> You need to join db#1's security group before you open db#2. You will then
> be able to assign permissions - permissions are not inherited on imported
> objects.
>
> Regards,
> Keith.
> www.keithwilby.com
>
>
>

Use Sandra Daigle's utility to dump and then load the permissions. Look for
DBUtilities 1.0 at
http://www.daiglenet.com/MSAccess.htm

--
Joan Wild
Microsoft Access MVP

REC wrote:
> Thanks and DOH! Do you know of any utilities that can copy the
> security settings? thx.
>
> "Keith" wrote:
>
>> "REC" <(E-Mail Removed)> wrote in message
>> newsFEA4230-D445-4E61-AC6D-(E-Mail Removed)...
>>> I'm trying to import objects from db#1 (secured) into a blank db#2
>>> (unsecured). I believe if I use the Workgroup Adminstrator to join
>>> db#1's mdw, I should be able to import from within db#2. I would
>>> prefer not to export from db#1 to db#2 because I can only export
>>> one object at a time.
>>>
>>> Once I've copied the objects, how would I go about copying the exact
>>> security settings from db#1 onto db#2? I'm troubleshooting
>>> corruption. That's why I'm moving to a blank database.
>>>
>>> I would appreciate your help. Thx.
>>
>> You need to join db#1's security group before you open db#2. You
>> will then be able to assign permissions - permissions are not
>> inherited on imported objects.
>>
>> Regards,
>> Keith.
>> www.keithwilby.com

Thanks for the tip.

"Joan Wild" wrote:

> Use Sandra Daigle's utility to dump and then load the permissions. Look for
> DBUtilities 1.0 at
> http://www.daiglenet.com/MSAccess.htm
>
> --
> Joan Wild
> Microsoft Access MVP
>
> REC wrote:
> > Thanks and DOH! Do you know of any utilities that can copy the
> > security settings? thx.
> >
> > "Keith" wrote:
> >
> >> "REC" <(E-Mail Removed)> wrote in message
> >> newsFEA4230-D445-4E61-AC6D-(E-Mail Removed)...
> >>> I'm trying to import objects from db#1 (secured) into a blank db#2
> >>> (unsecured). I believe if I use the Workgroup Adminstrator to join
> >>> db#1's mdw, I should be able to import from within db#2. I would
> >>> prefer not to export from db#1 to db#2 because I can only export
> >>> one object at a time.
> >>>
> >>> Once I've copied the objects, how would I go about copying the exact
> >>> security settings from db#1 onto db#2? I'm troubleshooting
> >>> corruption. That's why I'm moving to a blank database.
> >>>
> >>> I would appreciate your help. Thx.
> >>
> >> You need to join db#1's security group before you open db#2. You
> >> will then be able to assign permissions - permissions are not
> >> inherited on imported objects.
> >>
> >> Regards,
> >> Keith.
> >> www.keithwilby.com
>
>
>