Skip to main content
Inspiring
March 16, 2007
Question

"is not a valid path" error

  • March 16, 2007
  • 1 reply
  • 1026 views
I'm linking to a table from another dB in Access. The data show up fine in Access.
Then, in CF, I'm trying to join two tables to grab a subset of records.

I have the following query:

<cfquery name="q_Resp" datasource="req" dbtype="odbc">
SELECT r.id, r.role, r.name, t.term
FROM req_role r, term t
WHERE r.id = '#SESSION.PID#' and t.term = '20072'
</cfquery>

It seems like it should work, however, I'm getting this error which points to the linked table:

Error Executing Database Query.
[Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][ODBC Microsoft Access Driver] 'S:\records\BE.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.

Can anyone help?

Thx,

Rick
This topic has been closed for replies.

1 reply

Inspiring
March 16, 2007
The error has nothing to do with the query. Make sure your datasource is set up correctly on your administrator.

But since you posted your query, you don't need dbtype="odbc". Also, you are not joining your tables with any field. Is this what you want?

Also, is req_role.id really a character field?
Inspiring
March 16, 2007
Both datasources verify in the CF admin. Do you have a specific point to check in the CF Admin?

I went back and created a query in Access that works fine in Access. When I move it to CF, I get the same error. The FROM target is an Access Query which CF is finding. What is going on?

<cfquery name="q_getResp" datasource="req">
SELECT id, role, name
FROM enrolled
WHERE id = '#SESSION.PID#'
</cfquery>

Error Executing Database Query.
[Macromedia][SequeLink JDBC Driver][ODBC Socket][Microsoft][ODBC Microsoft Access Driver] 'S:\records\BE.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.

This is a valid path, if I copy the path in the CF error message and paste it into Windows Explorer, it tries to open the dB, no problem.
Inspiring
March 20, 2007
No one? Is there some issue about querying linked tables? As I said, the datasource in the error message is defined in the CF Admin and verifies fine.