write to database without giving write permission to IIS

[jyoti]

Hi there,
I have some ASP code that writes to access database. For
security reason I do not want IUSER to give write
permission to database folder. I am using IIS 5.0 and
vbscript.

Is there any way writing to access database can be done
without giving write permission to IUSER?
Is there any dll or com object or source code?

I appreciate your time.

Thanks
Jyoti

[Aaron [SQL Server MVP]]

Yes, give write permissions to a specific Windows user, and require Windows
Authentication to run the ASP pages.

Or, use a database product that doesn't require explicit file writing
permissions.

(No, "dll or com object" will not solve this problem. This is not an issue
of code techniques, it's a issue of Windows security and database platform
choice.)

--
[url]http://www.aspfaq.com/[/url]
(Reverse address to reply.)




"jyoti" <muhammed_rahman@hotmail.com> wrote in message
news:1675401c447f5$d7c33270$a401280a@phx.gbl...

> Hi there,
> I have some ASP code that writes to access database. For
> security reason I do not want IUSER to give write
> permission to database folder. I am using IIS 5.0 and
> vbscript.
>
> Is there any way writing to access database can be done
> without giving write permission to IUSER?
> Is there any dll or com object or source code?
>
> I appreciate your time.
>
> Thanks
> Jyoti
>

[Jeff Cochran]

On Tue, 1 Jun 2004 09:31:08 -0700, "jyoti"
<muhammed_rahman@hotmail.com> wrote:

>Hi there,
>I have some ASP code that writes to access database. For
>security reason I do not want IUSER to give write
>permission to database folder. I am using IIS 5.0 and
>vbscript.
>
>Is there any way writing to access database can be done
>without giving write permission to IUSER?

You have to give MODIFY permission to whatever user account is
accessing the database file *and* folder. That's a function of
Access, not IIS or ASP.

>Is there any dll or com object or source code?

Not that works around this. An Access database creates a temporary
lock file. That's why the user has to have rights to the folder as
well as the access file. My first choice would be to move from Access
to MSDE, or SQL Server if you can afford it. Second would be to use
an account as Aaron suggested, forcing a login with a separate Windows
account. It's not the anonymous user account, but the account still
has access to the folder.

Jeff