ASP --> OLEDB --> Access db ?

[Jeff Cochran]

On Wed, 3 Mar 2004 13:06:14 -0800, ChrisB
<anonymous@discussions.microsoft.com> wrote:

>I have an ASP page using OLEDB to connect to an Access97 db. In the Conn string I must use an explit path to the mdb, e.g. C:\inetpub\wwwroot\mydir\mydb.mdb - by doing this I also have to provide Read/Write to the NT INET user account to open file and query tables.
>
>Since I am dealing w/ an ISP hosting my app, it's not easy to call them and ask them to add rw perms on my virtual directory. Is there a way around this?

Don't use Access. :)

Access requires the user to have Modify or better permission on the
folder where the database MDB file is so the lock file can be created.
That's a limitation of Access, not the ASP or OLEDB.

Most hosts accomodate this in a control panel that allows you to hange
permissions for Access files. And you don't always need an explicit
path, but it won't make a difference on the permission requirement.

Jeff

[Roland Hall]

"ChrisB" wrote:
: I have an ASP page using OLEDB to connect to an Access97 db. In the Conn
string I must use an explit path to the mdb, e.g.
C:\inetpub\wwwroot\mydir\mydb.mdb

That is not actually correct. Your connect can be:
Server.MapPath("\mydir\mydb.mdb")

- by doing this I also have to provide Read/Write to the NT INET user
account to open file and query tables.

Nope. The directory where the database resides should have change or modify
rights. That is all that is needed.

: Since I am dealing w/ an ISP hosting my app, it's not easy to call them
and ask them to add rw perms on my virtual directory. Is there a way around
this?

If your host provides a control panel that allows you to make permission
changes on your directory structure, then you do not have to call them. You
can take care of it yourself. If not, then you have to call them or email
them. They may also offer DSN, but I would avoid that and instead use
OLEDB, which is what you're referring to.

Note that a lot of hosts put a db and/or a data directory as the same
directory level as wwwroot. So, the physical path may be:
c:\inetpub\db
c:\inetpub\data
c:\inetpub\wwwroot

If they have provided an area like this [db, data, both], then the
permissions are already set [generally] and you just have to locate your
database, chat logs, etc. there [db/data respectively]. Normally you will
have to use FTP to put the files there if you're publishing using FPSE
(Front Page Server Extensions). And, then you will have to use a physical
path because neither FPSE nor Server.MapPath work above or outside the
wwwroot.

When you signed up for this hosting account, you should have received an
email with all of the information you need to work with databases. If
you're hosted on a Linux box, then MS Access is NOT an option but MySQL may
be.

HTH...

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Technet Script Center - [url]http://www.microsoft.com/technet/scriptcenter/[/url]
WSH 5.6 Documentation - [url]http://msdn.microsoft.com/downloads/list/webdev.asp[/url]
MSDN Library - [url]http://msdn.microsoft.com/library/default.asp[/url]