We are having a weird problem involving Windows 2000 and Access 2000 SP-3.
When we compact the database it makes a new database as part of the
compacting, then deletes the old one and renames the compacted database.

The problem is that the new file does not have the same security settings as
the old file. I have checked the parent folder settings and everything is
set properly. It is set to place its attributes on any new files in the
folder via the Security tab Advanced settings.

Any help or ideas would be appreciated.

Thanks,
DAN

Nothing to do with the operating system. Ask in an access group.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]
Microsoft Certified Professional [Windows 2000]
http://www.microsoft.com/protect


"Danial E. Shappell" wrote:
| We are having a weird problem involving Windows 2000 and Access 2000 SP-3.
| When we compact the database it makes a new database as part of the
| compacting, then deletes the old one and renames the compacted database.
|
| The problem is that the new file does not have the same security settings
as
| the old file. I have checked the parent folder settings and everything is
| set properly. It is set to place its attributes on any new files in the
| folder via the Security tab Advanced settings.
|
| Any help or ideas would be appreciated.
|
| Thanks,
| DAN
|
|

Dan,

I'm a little bit fuzzy re your second paragraph. Are you saying that the
new file inherits the permissions of the folder, or that it does not? And
was the original database set to do so, and if so, did it?

In any case, can you confirm that this issue does or does not occur only to
this one particular Access database, or only in this particular folder?

--
John Phillips
MVP - Windows SDK


"Danial E. Shappell" <(E-Mail Removed)> wrote in message
news:ZlFYb.350438$na.519513@attbi_s04...
> We are having a weird problem involving Windows 2000 and Access 2000 SP-3.
> When we compact the database it makes a new database as part of the
> compacting, then deletes the old one and renames the compacted database.
>
> The problem is that the new file does not have the same security settings
as
> the old file. I have checked the parent folder settings and everything is
> set properly. It is set to place its attributes on any new files in the
> folder via the Security tab Advanced settings.
>
> Any help or ideas would be appreciated.
>
> Thanks,
> DAN
>
>

The new file does not inherit the permissions of the parent folder, it sets
up the owner on the new file as the person who is logged in and drops the
security group that gave this logged in user the ability to open the
database in the first place. This sets it up so that only the person who
compacted the database or an administrator is able to open it.

Does this clarify things?

DAN

"John Phillips" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Dan,
>
> I'm a little bit fuzzy re your second paragraph. Are you saying that the
> new file inherits the permissions of the folder, or that it does not? And
> was the original database set to do so, and if so, did it?
>
> In any case, can you confirm that this issue does or does not occur only
to
> this one particular Access database, or only in this particular folder?
>
> --
> John Phillips
> MVP - Windows SDK
>
>
> "Danial E. Shappell" <(E-Mail Removed)> wrote in message
> news:ZlFYb.350438$na.519513@attbi_s04...
> > We are having a weird problem involving Windows 2000 and Access 2000
SP-3.
> > When we compact the database it makes a new database as part of the
> > compacting, then deletes the old one and renames the compacted database.
> >
> > The problem is that the new file does not have the same security
settings
> as
> > the old file. I have checked the parent folder settings and everything
is
> > set properly. It is set to place its attributes on any new files in the
> > folder via the Security tab Advanced settings.
> >
> > Any help or ideas would be appreciated.
> >
> > Thanks,
> > DAN
> >
> >
>
>