compacting the db

[Armin]

Everytime I compact the db the file changes permission
from everyone to system,admin & to user who used the db.OS
is win2000 on NTFS.If I don't compact everything is fine.

Thanks in advance

[Van T. Dinh]

All db users should have Read/Write/Create/Delete on the Directory which is
cascaded to the files in the Directory.

The reason is that when you compact a database, Access/JET actually creates
a temporary database "dbX.mdb" (starting with X=1), write all objects from
the existing db, delete the existing db and then rename the "dbX.mdb" to the
old name. Thus after you compact, it is actually a *different* file, NOT
the original file and the new file carries different permission if the
Directory has different permission.

--
HTH
Van T. Dinh
MVP (Access)



"Armin" <a@a.com> wrote in message
news:00b101c33dac$89335da0$a501280a@phx.gbl...

> Everytime I compact the db the file changes permission
> from everyone to system,admin & to user who used the db.OS
> is win2000 on NTFS.If I don't compact everything is fine.
>
> Thanks in advance
>
>

[Alick [MSFT]]

Hi,

Van has explained the situation; it seems it is by design, the compact
process always compacts the source file into a new file, even if you
compact the file in place in Microsoft Access. When the new file is
created, it automatically inherits the default NTFS permissions for new
files in that particular folder. Custom NTFS permissions are not migrated
from the source file to the target file. If your computer is using
Access2002 , You can find the public Knowledge Base at :

295234 ACC2002: Compacting File Resets NTFS Permissions

[url]http://support.microsoft.com/?id=295234[/url]

If your computer is using Access 2000 , It is probably that the new file
will take/ inherit the security property of the Temp folder of the User
of the server machine.

You can try the following steps to give the permissions which source
database file has to the new file.

1 go to C:\Documents and Settings\<User1>\Local Settings\Temp (where
<User1> is one of your users)

2. Right mouse click and go to Properties

3. Select the Security tab and add the permissions which your source
database file has to the folder

4. Test compacting the database again

Hope it helps.


Sincerely,

Alick Ye, MCSD
Product Support Services
Microsoft Corporation
Get Secure! - <www.microsoft.com/security>

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Content-Class: urn:content-classes:message
| X-Tomcat-NG: microsoft.public.access.forms
|
| They have full permission and still after compacting it
| changes to SYSTEM,ADMIN and user who worked on the DB.
|
|
|
|
| >-----Original Message-----
| >All db users should have Read/Write/Create/Delete on the
| Directory which is
| >cascaded to the files in the Directory.
| >
| >The reason is that when you compact a database,
| Access/JET actually creates
| >a temporary database "dbX.mdb" (starting with X=1), write
| all objects from
| >the existing db, delete the existing db and then rename
| the "dbX.mdb" to the
| >old name. Thus after you compact, it is actually a
| *different* file, NOT
| >the original file and the new file carries different
| permission if the
| >Directory has different permission.
| >
| >--
| >HTH
| >Van T. Dinh
| >MVP (Access)
| >
| >
| >
| >"Armin" <a@a.com> wrote in message
| >news:00b101c33dac$89335da0$a501280a@phx.gbl...
| >> Everytime I compact the db the file changes permission
| >> from everyone to system,admin & to user who used the
| db.OS
| >> is win2000 on NTFS.If I don't compact everything is
| fine.
| >>
| >> Thanks in advance
| >>
| >>
| >
| >
| >.
| >
|