Stiebel Eltron
asked on
How to locate the path of Access db in Map Network Drive location?
Dear EE Experts,
We would like to ask for tech support, this may be related to our previous thread, but here's the case.
We already mapped the network drive where the access db is located, we set it as Drive P:
and inside that drive you'll see the db we need to pull out.
Kindly advise on how to locate it here:
<%
connectString = "Provider=Microsoft.Jet.OL EDB.4.0;Da ta Source=" & Server.MapPath("products.m db")
Set myConnection = Server.CreateObject("ADODB .Connectio n")
-------------------------- ---------- ---------- ---------- ---------- ---------- ---------- ------
The location of the web files is different from the location of the db...
Web files are in Drive K:
If I just use that ("products.mdb"), it will show the old db that is INCLUDED on that web files folder...
Please help...
We would like to ask for tech support, this may be related to our previous thread, but here's the case.
We already mapped the network drive where the access db is located, we set it as Drive P:
and inside that drive you'll see the db we need to pull out.
Kindly advise on how to locate it here:
<%
connectString = "Provider=Microsoft.Jet.OL
Set myConnection = Server.CreateObject("ADODB
--------------------------
The location of the web files is different from the location of the db...
Web files are in Drive K:
If I just use that ("products.mdb"), it will show the old db that is INCLUDED on that web files folder...
Please help...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
@thewild: sorry but your advise didn't work... I did it already, put the machine name or even its IP, it didn't work...
Your ASP pages are executed under a special account (probably ASP.NET account, or IUSR_<servername> account). This account does not see mapped drives, these are only seen by real logged on users.
Furthermore, this not will not have, by default, access to the network share.
You could give the user running ASP scripts the right to access this network share, and change Server.MapPath("products.m
You must understand though that giving this IIS user access to a network share is very bad practice security-wise.