problems with linked access tables in ASP

[Laura]

Hello,

I've seen this posting many times, but there are no responses to it...
I hope it's not too difficult to fix.

I have two databases, one primary one, and another one which contains
a table that I need to use. So, I linked the table I need in the
secondary db to the primary database. Now, when I try to create a
recordset object to it in ASP, I get the following error:

Microsoft][ODBC Microsoft Access Driver] 'V:\DB\Conf.mdb' is not a
valid path. Make sure that the path name is spelled correctly and that
you are connected to the server on which the file resides.


Conf.mdb is the secondary database that contains the table originally.
The connection that I have is to the primary database.

I really don't know what's going on, since all the other tables in the
db (that are not linked from somewhere else) work perfectly and I can
read information form them through ASP.

Thanks for any help,
Laura

[Ken Schaefer]

Drive letters are mapped for the logged on user only. So, just because you
logon and map drive v: doesn't mean that it is mapped for *other* users,
including IUSR_<machinename>

Suggest you use UNC naming instead: \\server\share\conf.mdb

Cheers
Ken

"Laura" <salamahl@aecl.ca> wrote in message
news:3b666b7a.0308181117.2f87d097@posting.google.c om...
: Hello,
:
: I've seen this posting many times, but there are no responses to it...
: I hope it's not too difficult to fix.
:
: I have two databases, one primary one, and another one which contains
: a table that I need to use. So, I linked the table I need in the
: secondary db to the primary database. Now, when I try to create a
: recordset object to it in ASP, I get the following error:
:
: Microsoft][ODBC Microsoft Access Driver] 'V:\DB\Conf.mdb' is not a
: valid path. Make sure that the path name is spelled correctly and that
: you are connected to the server on which the file resides.
:
:
: Conf.mdb is the secondary database that contains the table originally.
: The connection that I have is to the primary database.
:
: I really don't know what's going on, since all the other tables in the
: db (that are not linked from somewhere else) work perfectly and I can
: read information form them through ASP.
:
: Thanks for any help,
: Laura

[Laura]

Ok, I tried getting that to work, but the problem now lies with access.

I didn't specifically hard code in the path to the secondary database
(V:/.../Conf.mdb). There is a table in that database that is linked to
another one (\\server\..\mainDatabase.mdb). So, the problem lies with I
link table in Conf.mdb to mainDatabase.mdb, since access uses the "V:/"
path.

So, any ideas how I can get around that? I tried typing in the UNC path,
but it just told me that the database couldn't be found, invalid path.

Thanks so much!
Laura


"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message news:<esKdVafZDHA.736@TK2MSFTNGP09.phx.gbl>...

> Drive letters are mapped for the logged on user only. So, just because you
> logon and map drive v: doesn't mean that it is mapped for *other* users,
> including IUSR_<machinename>
>
> Suggest you use UNC naming instead: \\server\share\conf.mdb
>
> Cheers
> Ken
>
> "Laura" <salamahl@aecl.ca> wrote in message
> news:3b666b7a.0308181117.2f87d097@posting.google.c om...
> : Hello,
> :
> : I've seen this posting many times, but there are no responses to it...
> : I hope it's not too difficult to fix.
> :
> : I have two databases, one primary one, and another one which contains
> : a table that I need to use. So, I linked the table I need in the
> : secondary db to the primary database. Now, when I try to create a
> : recordset object to it in ASP, I get the following error:
> :
> : Microsoft][ODBC Microsoft Access Driver] 'V:\DB\Conf.mdb' is not a
> : valid path. Make sure that the path name is spelled correctly and that
> : you are connected to the server on which the file resides.
> :
> :
> : Conf.mdb is the secondary database that contains the table originally.
> : The connection that I have is to the primary database.
> :
> : I really don't know what's going on, since all the other tables in the
> : db (that are not linked from somewhere else) work perfectly and I can
> : read information form them through ASP.
> :
> : Thanks for any help,
> : Laura

[JOhn Beschler]

I just tested what I believe is your scenerio and it
worked perfectly.

DB1: C:\Inetpub\wwwroot\practice.mdb
DB2: C:\Documents and settings\user\my documents\coe.mdb


DB1 contains a link to table COE in DB2.

Here's the ASP code:
strConn = "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Inetpub\wwwroot\practice.mdb;Persist Security
Info=False"
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.Open strConn

Set objRS = Server.CreateObject("ADODB.Recordset")
objRS.Open "COEs", objConn, 3, 3
Response.Write "<table cellpadding=2 cellspacing=0
border=1>" & vbcrlf
Response.Write " <tr>" & vbcrlf
For Each Field In objRS.Fields
Response.Write " <th>" & Field.Name & "</th>" &
vbcrlf
Next
Response.Write " </tr>" & vbcrlf
Do While Not objRS.Eof
Response.Write " <tr>" & vbcrlf
For Each Field In objRS.Fields
Response.Write " <td>" & Field.Value & "</td>" &
vbcrlf
Next
Response.Write " </tr>" & vbcrlf
objRS.MoveNext
Loop
Response.Write "</table>" & vbcrlf
strAction = ""



The output is the contents of the COE table as it should
be.

Even tried it with an access database residing on a
completely different computer. Still works.

I suspect your error is in connecting to the first DB not
the linked DB.
Try reading the contents of a table in the main DB and see
if you are able to do that. Once you get that working,
accessing the linked table should be nothing more than
changing the table name in the SQL statement.

HTH,
John

>-----Original Message-----
>Ok, I tried getting that to work, but the problem now

lies with access.

>
>I didn't specifically hard code in the path to the

secondary database

>(V:/.../Conf.mdb). There is a table in that database that

is linked to

>another one (\\server\..\mainDatabase.mdb). So, the

problem lies with I

>link table in Conf.mdb to mainDatabase.mdb, since access

uses the "V:/"

>path.
>
>So, any ideas how I can get around that? I tried typing

in the UNC path,

>but it just told me that the database couldn't be found,

invalid path.

>
>Thanks so much!
>Laura
>
>
>"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in

message news:<esKdVafZDHA.736@TK2MSFTNGP09.phx.gbl>...

>> Drive letters are mapped for the logged on user only.

So, just because you

>> logon and map drive v: doesn't mean that it is mapped

for *other* users,

>> including IUSR_<machinename>
>>
>> Suggest you use UNC naming instead:

\\server\share\conf.mdb

>>
>> Cheers
>> Ken
>>
>> "Laura" <salamahl@aecl.ca> wrote in message
>> news:3b666b7a.0308181117.2f87d097@posting.google.c om...
>> : Hello,
>> :
>> : I've seen this posting many times, but there are no

responses to it...

>> : I hope it's not too difficult to fix.
>> :
>> : I have two databases, one primary one, and another

one which contains

>> : a table that I need to use. So, I linked the table I

need in the

>> : secondary db to the primary database. Now, when I

try to create a

>> : recordset object to it in ASP, I get the following

error:

>> :
>> : Microsoft][ODBC Microsoft Access

Driver] 'V:\DB\Conf.mdb' is not a

>> : valid path. Make sure that the path name is spelled

correctly and that

>> : you are connected to the server on which the file

resides.

>> :
>> :
>> : Conf.mdb is the secondary database that contains the

table originally.

>> : The connection that I have is to the primary

database.

>> :
>> : I really don't know what's going on, since all the

other tables in the

>> : db (that are not linked from somewhere else) work

perfectly and I can

>> : read information form them through ASP.
>> :
>> : Thanks for any help,
>> : Laura

>.
>

[Laura]

hmmm... now I'm really confused. I tried starting from scratch, just
to see if my original connection isn't right, and nothing.

My original connection was slightly different (Sytem DSN) but it
worked with all the tables/queries that are native to the database,
just not the linked table. So, I basically copied and pasted your code
and it worked exactly the same way.

this is my error:

'V:\REVAMPED\DB\Conf.mdb' is not a valid path. Make sure that the path
name is spelled correctly and that you are connected to the server on
which the file resides.

I don't hard code this path in (v:/revamped...). In my connection, I
have the UNC path to the main database, and this is the secondary
database.

I'm not sure, but I think I need to somehow make MS Access link to the
database using the UNC path.

thanks so much in advance!



"JOhn Beschler" <giles@geewhiz.com> wrote in message news:<038201c36695$65ed5a00$a501280a@phx.gbl>...

> I just tested what I believe is your scenerio and it
> worked perfectly.
>
> DB1: C:\Inetpub\wwwroot\practice.mdb
> DB2: C:\Documents and settings\user\my documents\coe.mdb
>
>
> DB1 contains a link to table COE in DB2.
>
> Here's the ASP code:
> strConn = "Provider=Microsoft.Jet.OLEDB.4.0;Data
> Source=C:\Inetpub\wwwroot\practice.mdb;Persist Security
> Info=False"
> Set objConn = Server.CreateObject("ADODB.Connection")
> objConn.Open strConn
>
> Set objRS = Server.CreateObject("ADODB.Recordset")
> objRS.Open "COEs", objConn, 3, 3
> Response.Write "<table cellpadding=2 cellspacing=0
> border=1>" & vbcrlf
> Response.Write " <tr>" & vbcrlf
> For Each Field In objRS.Fields
> Response.Write " <th>" & Field.Name & "</th>" &
> vbcrlf
> Next
> Response.Write " </tr>" & vbcrlf
> Do While Not objRS.Eof
> Response.Write " <tr>" & vbcrlf
> For Each Field In objRS.Fields
> Response.Write " <td>" & Field.Value & "</td>" &
> vbcrlf
> Next
> Response.Write " </tr>" & vbcrlf
> objRS.MoveNext
> Loop
> Response.Write "</table>" & vbcrlf
> strAction = ""
>
>
>
> The output is the contents of the COE table as it should
> be.
>
> Even tried it with an access database residing on a
> completely different computer. Still works.
>
> I suspect your error is in connecting to the first DB not
> the linked DB.
> Try reading the contents of a table in the main DB and see
> if you are able to do that. Once you get that working,
> accessing the linked table should be nothing more than
> changing the table name in the SQL statement.
>
> HTH,
> John
>
>
>
>

> >-----Original Message-----
> >Ok, I tried getting that to work, but the problem now

> lies with access.

> >
> >I didn't specifically hard code in the path to the

> secondary database

> >(V:/.../Conf.mdb). There is a table in that database that

> is linked to

> >another one (\\server\..\mainDatabase.mdb). So, the

> problem lies with I

> >link table in Conf.mdb to mainDatabase.mdb, since access

> uses the "V:/"

> >path.
> >
> >So, any ideas how I can get around that? I tried typing

> in the UNC path,

> >but it just told me that the database couldn't be found,

> invalid path.

> >
> >Thanks so much!
> >Laura
> >
> >
> >"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in

> message news:<esKdVafZDHA.736@TK2MSFTNGP09.phx.gbl>...

> >> Drive letters are mapped for the logged on user only.

> So, just because you

> >> logon and map drive v: doesn't mean that it is mapped

> for *other* users,

> >> including IUSR_<machinename>
> >>
> >> Suggest you use UNC naming instead:

> \\server\share\conf.mdb

> >>
> >> Cheers
> >> Ken
> >>
> >> "Laura" <salamahl@aecl.ca> wrote in message
> >> news:3b666b7a.0308181117.2f87d097@posting.google.c om...
> >> : Hello,
> >> :
> >> : I've seen this posting many times, but there are no

> responses to it...

> >> : I hope it's not too difficult to fix.
> >> :
> >> : I have two databases, one primary one, and another

> one which contains

> >> : a table that I need to use. So, I linked the table I

> need in the

> >> : secondary db to the primary database. Now, when I

> try to create a

> >> : recordset object to it in ASP, I get the following

> error:

> >> :
> >> : Microsoft][ODBC Microsoft Access

> Driver] 'V:\DB\Conf.mdb' is not a

> >> : valid path. Make sure that the path name is spelled

> correctly and that

> >> : you are connected to the server on which the file

> resides.

> >> :
> >> :
> >> : Conf.mdb is the secondary database that contains the

> table originally.

> >> : The connection that I have is to the primary

> database.

> >> :
> >> : I really don't know what's going on, since all the

> other tables in the

> >> : db (that are not linked from somewhere else) work

> perfectly and I can

> >> : read information form them through ASP.
> >> :
> >> : Thanks for any help,
> >> : Laura

> >.
> >

[John Beschler]

Remember that your ASP pages do not run in the same
context as you. In otherwords, when you create the link to
the 2nd table in Access, you are probably logged in as
yourself; however, when you ASP page runs it is
authenticted as (usually) IWAM_computername. You need to
make sure that the IWAM_computername user has appropriate
permissions on the 2nd MDB file and that the drive
mappings are the same.

>-----Original Message-----
>hmmm... now I'm really confused. I tried starting from

scratch, just

>to see if my original connection isn't right, and nothing.
>
>My original connection was slightly different (Sytem DSN)

but it

>worked with all the tables/queries that are native to the

database,

>just not the linked table. So, I basically copied and

pasted your code

>and it worked exactly the same way.
>
>this is my error:
>
>'V:\REVAMPED\DB\Conf.mdb' is not a valid path. Make sure

that the path

>name is spelled correctly and that you are connected to

the server on

>which the file resides.
>
>I don't hard code this path in (v:/revamped...). In my

connection, I

>have the UNC path to the main database, and this is the

secondary

>database.
>
>I'm not sure, but I think I need to somehow make MS

Access link to the

>database using the UNC path.
>
>thanks so much in advance!
>
>
>
>"JOhn Beschler" <giles@geewhiz.com> wrote in message

news:<038201c36695$65ed5a00$a501280a@phx.gbl>...

>> I just tested what I believe is your scenerio and it
>> worked perfectly.
>>
>> DB1: C:\Inetpub\wwwroot\practice.mdb
>> DB2: C:\Documents and settings\user\my documents\coe.mdb
>>
>>
>> DB1 contains a link to table COE in DB2.
>>
>> Here's the ASP code:
>> strConn = "Provider=Microsoft.Jet.OLEDB.4.0;Data
>> Source=C:\Inetpub\wwwroot\practice.mdb;Persist Security
>> Info=False"
>> Set objConn = Server.CreateObject("ADODB.Connection")
>> objConn.Open strConn
>>
>> Set objRS = Server.CreateObject("ADODB.Recordset")
>> objRS.Open "COEs", objConn, 3, 3
>> Response.Write "<table cellpadding=2 cellspacing=0
>> border=1>" & vbcrlf
>> Response.Write " <tr>" & vbcrlf
>> For Each Field In objRS.Fields
>> Response.Write " <th>" & Field.Name & "</th>" &
>> vbcrlf
>> Next
>> Response.Write " </tr>" & vbcrlf
>> Do While Not objRS.Eof
>> Response.Write " <tr>" & vbcrlf
>> For Each Field In objRS.Fields
>> Response.Write " <td>" & Field.Value

& "</td>" &

>> vbcrlf
>> Next
>> Response.Write " </tr>" & vbcrlf
>> objRS.MoveNext
>> Loop
>> Response.Write "</table>" & vbcrlf
>> strAction = ""
>>
>>
>>
>> The output is the contents of the COE table as it

should

>> be.
>>
>> Even tried it with an access database residing on a
>> completely different computer. Still works.
>>
>> I suspect your error is in connecting to the first DB

not

>> the linked DB.
>> Try reading the contents of a table in the main DB and

see

>> if you are able to do that. Once you get that working,
>> accessing the linked table should be nothing more than
>> changing the table name in the SQL statement.
>>
>> HTH,
>> John
>>
>>
>>
>>

>> >-----Original Message-----
>> >Ok, I tried getting that to work, but the problem now

>> lies with access.

>> >
>> >I didn't specifically hard code in the path to the

>> secondary database

>> >(V:/.../Conf.mdb). There is a table in that database

that

>> is linked to

>> >another one (\\server\..\mainDatabase.mdb). So, the

>> problem lies with I

>> >link table in Conf.mdb to mainDatabase.mdb, since

access

>> uses the "V:/"

>> >path.
>> >
>> >So, any ideas how I can get around that? I tried

typing

>> in the UNC path,

>> >but it just told me that the database couldn't be

found,

>> invalid path.

>> >
>> >Thanks so much!
>> >Laura
>> >
>> >
>> >"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote

in

>> message news:<esKdVafZDHA.736@TK2MSFTNGP09.phx.gbl>...

>> >> Drive letters are mapped for the logged on user

only.

>> So, just because you

>> >> logon and map drive v: doesn't mean that it is

mapped

>> for *other* users,

>> >> including IUSR_<machinename>
>> >>
>> >> Suggest you use UNC naming instead:

>> \\server\share\conf.mdb

>> >>
>> >> Cheers
>> >> Ken
>> >>
>> >> "Laura" <salamahl@aecl.ca> wrote in message
>> >>

news:3b666b7a.0308181117.2f87d097@posting.google.c om...

>> >> : Hello,
>> >> :
>> >> : I've seen this posting many times, but there are

no

>> responses to it...

>> >> : I hope it's not too difficult to fix.
>> >> :
>> >> : I have two databases, one primary one, and another

>> one which contains

>> >> : a table that I need to use. So, I linked the

table I

>> need in the

>> >> : secondary db to the primary database. Now, when I

>> try to create a

>> >> : recordset object to it in ASP, I get the following

>> error:

>> >> :
>> >> : Microsoft][ODBC Microsoft Access

>> Driver] 'V:\DB\Conf.mdb' is not a

>> >> : valid path. Make sure that the path name is

spelled

>> correctly and that

>> >> : you are connected to the server on which the file

>> resides.

>> >> :
>> >> :
>> >> : Conf.mdb is the secondary database that contains

the

>> table originally.

>> >> : The connection that I have is to the primary

>> database.

>> >> :
>> >> : I really don't know what's going on, since all the

>> other tables in the

>> >> : db (that are not linked from somewhere else) work

>> perfectly and I can

>> >> : read information form them through ASP.
>> >> :
>> >> : Thanks for any help,
>> >> : Laura
>> >.
>> >

>.
>

[Laura]

Ok, how do I change the IWAM_computername permissions? (what does IWAM
stand for, btw?)

I changed all the other permissions on both databases to be change/full
control, but the error still appears.

thanks, I think we're getting closer!

Laura


*** Sent via Developersdex [url]http://www.developersdex.com[/url] ***
Don't just participate in USENET...get rewarded for it!