Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 311
  • Last Modified:

Cannot find table or query error with SQL connection string in query and ODBC table

I an getting the error cannot find the input table or query ".." when trying to run my query. The query uses  ODBC linked tables and local tables. I put the connection string in the query. The name is correct. The ODBC connection is not a trusted connection. Everything works fine in my test environment with a standard ODBC setup. These are read-only tables from another server. The tables open just fine and display data. These queries are used in reports and display fields on forms. Without the connection string, the user is asked for the login a zillion times. I attached a screen shot of the error and the SQL in the query. What am I missing? Is there another setting I have to do on either side? I don't control the server. Thanks!
Doc1-3.doc
0
gaynes
Asked:
gaynes
  • 6
  • 6
1 Solution
 
dqmqCommented:
You seem to be missing end-quotes to terminate the connection string before the WHERE clause.
0
 
dqmqCommented:
Putting connection string in the query is highly unusual; I'm not clear why you don't simply use linked tables or passthru queries.    
0
 
gaynesAuthor Commented:
The SQL is Access written. I do use linked tables, but since it isn't a trusted connection I have to use the connection string. I don't think a passthru query would act any differently.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
dqmqCommented:
>I do use linked tables, but since it isn't a trusted connection I have to use the connection string.  

Actually, the connection string is assembled from the DSN and the query.  You can put the userid, password, and database in the DSN, then you don't need any of it in the query.  Furthermore, then you can also link to the tables without prompting for that information.

 
0
 
gaynesAuthor Commented:
That is what I did. It is in the query properties.It still gives the error message. If you look at my example you can see that.
0
 
dqmqCommented:
When I look at the example, I see a userid, password and database originating in the query.   I'm suggesting that you specify those things in the DSN, instead. That way you can link to the tables via the DSN without being prompted for userid/password.  The query can just reference the tablename without the IN clause and the connection string overrides embedded in it.

 
0
 
gaynesAuthor Commented:
 The person who set it up (IT person at the client) tells me he did. Since it is not a trusted connection, it will not retain the password so has to be put here as well. The tables can be opened with no problem outside the query. They are linked via ODBC.
0
 
dqmqCommented:
I apologize for haranging you so much about the DSN since it doesn't directly cause your problem.   Have you tried adding the end-quote as suggested earlier?

As for the getting the connection string out of the query: it can be done, but it's a little more complicated than I led you to believe, since the password you enter on the ODBC control panel is not saved. Let me know if you want to pursue





0
 
gaynesAuthor Commented:
The end quote is not an issue as the query was created in Access and works. The password works. The issue is that now it says it doesn't see a table that is there, is spelled correctly, and does open.
0
 
dqmqCommented:
On the user's machine Open the linked table in design view and click past all the warnings that you cannot change it.  Click on the title bar an then View properties.  What appears in the Description property?




0
 
gaynesAuthor Commented:
I have to get to the client's machine. I won't be able to do that until Monday.
0
 
gaynesAuthor Commented:
Figured it out - the error message was valid - it was referring to the name of the table on the SQL database referred to in the connection string. The query was using the linked table name in the database, dbo_+table name. Once I corrected that, it worked. Also, in 2007, connecting them and putting in the pw even though not a trusted connection, seems to store the pw. Thanks for trying.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now