Directory permissions to accommodate MSAccess

I have two programs that run fine at seperate times:
(1) perl programs that populuate an MSAccess database using ODBC running
from various user accounts including Administrator (I probably should not be
using Administrator, but this is not a production machine)
(2) ASP.NET programs running in the ISR_MACHINENAME account.

When the perl programs are not running (they take about 12 hours to run and
they run daily) my ASP.NET app runs great. It creates the ldb file,
presumably with the ISR_MACHINENAME account since I have not created a
web.config file.

When the perl programs are running populating the database, the ASP.NET
program dies because the MSAccess ldb files cannot be accessed by the
IUSR_MACHINENAME account. It complains that it cannot lock the file. If I
manually grant full control to the ISR_MACHINENAME account to the temporary
ldb file, the ASP.NET page loads fine.

So I posted a query in the MSAccess news group and was informed that the ldb
file is created with the security settings inherited from the containing
directory. Hmmmm.... Is this true? If this was true, then I would not
experience different behaviour depending which account opened the mdb/ldb
file first.

Well anyway, does someone have a solution?

Thanks,
Siegfried

Files created in a folder will inherit permissions (by default) unless you
explicitly block inheritance. Obviously the Creator/Owner will be identity
of whichever process created the file.

Cheers
Ken

"Siegfried Heintze" <siegfried.DeleteThis@heintze.com> wrote in message
news:OX%230jV21FHA.664@tk2msftngp13.phx.gbl...
:I have two programs that run fine at seperate times:
: (1) perl programs that populuate an MSAccess database using ODBC running
: from various user accounts including Administrator (I probably should not
be
: using Administrator, but this is not a production machine)
: (2) ASP.NET programs running in the ISR_MACHINENAME account.
:
: When the perl programs are not running (they take about 12 hours to run
and
: they run daily) my ASP.NET app runs great. It creates the ldb file,
: presumably with the ISR_MACHINENAME account since I have not created a
: web.config file.
:
: When the perl programs are running populating the database, the ASP.NET
: program dies because the MSAccess ldb files cannot be accessed by the
: IUSR_MACHINENAME account. It complains that it cannot lock the file. If I
: manually grant full control to the ISR_MACHINENAME account to the
temporary
: ldb file, the ASP.NET page loads fine.
:
: So I posted a query in the MSAccess news group and was informed that the
ldb
: file is created with the security settings inherited from the containing
: directory. Hmmmm.... Is this true? If this was true, then I would not
: experience different behaviour depending which account opened the mdb/ldb
: file first.
:
: Well anyway, does someone have a solution?
:
: Thanks,
: Siegfried
:
: