DB Compact causes loss of Windows file permissions

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm not sure if this is the correct group for this post so please let me know
if it isn't.

I have an Access 2000 database program with a frontend and backend. I have
recently added functionality for compact/repair to the distributed version of
this program. The compact/repair is executed by setting the 'Compact on
close' option in the frontend and/or running a batch file that executes each
database file with the /compact option.

The problem is that either of these methods causes the resulting database
file(s) to no longer 'inherit permissions from the parent...'. I have to
manually edit the Windows properties for the file(s) and recheck the 'inherit
permissions...' box.

So far I have only tested this on Win2K (SP3) so I don't know if it happens
on other OS yet.

Any thoughts/suggestions are greatly appreciated.
 
Hi, Jean.
The problem is that either of these methods causes the resulting database
file(s) to no longer 'inherit permissions from the parent...'. I have to
manually edit the Windows properties for the file(s) and recheck the 'inherit
permissions...' box.
Click to expand...

Michael Kaplan has placed an article about this subject on his Web site, as
well as a work-around. Please see the following Web page:

http://www.trigeminal.com/usenet/usenet028.asp
Any thoughts/suggestions are greatly appreciated.
Click to expand...

Don't forget that this inherited NT security permissions behavior will
change when your organization upgrades either the operating system or the
version of Access, so any fix you incorporate now will need to be addressed
(and tested) again prior to that migration.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Thank you for the info.

'69 Camaro said:
Hi, Jean.


Michael Kaplan has placed an article about this subject on his Web site, as
well as a work-around. Please see the following Web page:

http://www.trigeminal.com/usenet/usenet028.asp


Don't forget that this inherited NT security permissions behavior will
change when your organization upgrades either the operating system or the
version of Access, so any fix you incorporate now will need to be addressed
(and tested) again prior to that migration.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
Click to expand...
 
You need to look at the default permissions for new files.

Note that ldb files will also get the default permissions
for new files each time the database is opened. If the
default permission for new files is that they do not inherit
permissions from the parent, your LDB files won't inherit
permissions either.

(david)
 
Where do I look for the default permissions settings?

I don't know. On my PC I can't even see permissions. I'm
not an Admin person. Perhaps you have the 'folder' permissions
set differently from the 'file' permissions on the files
in the folder?

(david)
 
The .ldb files have the correct permissions. Only the new files created from
the compact utility do not inherit the parent permissions.
 
Jean said:
The .ldb files have the correct permissions. Only the new files
created from the compact utility do not inherit the parent
permissions.
Click to expand...

Right-click the folder, and choose properties. Check on the security tab
and then Advanced. Ensure that

'reset permissions on all child objects and enable propagation of
inheritable permissions'
is checked.
 
I did as you suggested but it didn't make any difference. The new files
created by the compact utility still do not have 'inherit permissions from
parent...' set.
 
Jean said:
I did as you suggested but it didn't make any difference. The new
files created by the compact utility still do not have 'inherit
permissions from parent...' set.
Click to expand...

Check the properties for the file as well that it's set to inherit
permissions from the parent.
 
It isn't. That's my problem. The file(s) originally are set to 'inherit
permissions...' but after the compact utility is run, the newly created
file(s) no longer have the 'inherit permissions..' box checked.
 
Jean said:
It isn't. That's my problem. The file(s) originally are set to
'inherit permissions...' but after the compact utility is run, the
newly created file(s) no longer have the 'inherit permissions..' box
checked.
Click to expand...

Then check the parent folder, and its parent folder. It is being propagated
from somewhere up the path.
 
Making changes to permissions upstream has no affect on the mdb files. If the
problem is due to an upstream permission situation why do the .ldb files have
the 'inherit permissions...' box checked but the .mdb files don't after the
compact utility is run?
 
Back
Top