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

x
  • Status: Solved
  • Priority: Medium
  • Security: Private
  • Views: 25
  • Last Modified:

MS Access ODBC issue

Tried to run a report in an Access database. The result was an ODBC call failed. The report data source is a linked SQL table. The ODBC bridge tests successfully. Could the issue be the connection string ? The SQL tables were linked on a different machine . Both machines are using a DSN that is using Windows authentication. Thanks.
0
StampIT
Asked:
StampIT
1 Solution
 
ThomasMcA2Commented:
Yes, it certainly could be the connection string. Check out connectionstrings.com for suggested connection strings to various back-end systems.
0
 
Kelvin SparksCommented:
Can you open the tables by themselves?
Are there views that may not have relinked. Is there any connection strings stored in VBA that need amendment?
Did the report work on the original machine that the relinking was done on?

Generally, as long as the server name and database name are the same from all locations, it shouldn't matter what machine it was linked from.


Kelvin
0
 
StampITAuthor Commented:
I neglected to mention that the machine I'm trying to run this on is using a  run time version of Access not a full version so I cannot open tables.

No views. No VBA connection strings.

The report does work on the original machine.
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!

 
Kelvin SparksCommented:
Using a runtime shouldn't make any difference. I regularly ship databases to be used in runtimes, connected to SQL Server without any issue. The only difference here is I use DSN-less connections - to save issues installing DSN's. At the end of the day though, they are both ODBC connections.

Have you tested locally in a runtime?


Kelvin
0
 
Dale FyeCommented:
The other thing you might be experiencing is a timeout.

Is the report based on a table or a query?  If a Query, you might need to change the ODBC timeout from the default (usually 60) to some other value.  Zero (0) will allow the query to run until completion, regardless of how long it takes.
0
 
StampITAuthor Commented:
The issue has been resolved. I did not know it at the time but I had installed the DNS and the database on an XP computer. When I installed on a Windows 7 machine every thing worked fine. Not sure how to handle this. Should I delete the question ?

Thanks for all the help.
0
 
Kelvin SparksCommented:
An XP computer should not have made any difference (assuming it was SP3)


Kelvin
0
 
StampITAuthor Commented:
Kelvin,

The operating system is XP SP3. All I can tell you is it did not work on XP and worked on Windows 7. Could it have something to do with version of Access runtime ? Thanks.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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