Missing ODBC definition causing Access Query to Fail - ms-access

We have a user that is trying to run an Access query on a new laptop and it's failing with an ODBC error. They obviously don't have the required odbc definition(s) on the new laptop.
How can I get the odbc name the query is using from Access? We can't figure out what name it's looking for so we can recreate it.
We're using Access for Office 365 MSO.

Related

What is wrong in my setup of a Pervasive ODBC connection from Access?

I'm trying to connect an Access 2010 database to a Pervasive dataset. My computer is Windows 7 32 bit. I've set up an ODBC connection through the ODBC administrator, but when I try to open a table in Access 2010 I get a message saying the ODBC connection has failed. What am I doing wrong?
So I've set up an ODBC connection. When I test it, the test completes successfully.
Then I go to Access and use the linked table manager to change the link to the database. The link seems to be refreshed successfully.
However, when I try to open the table, I get a message saying "ODBC-call failed" with no further information
Also, I can open the Pervasive client on my machine and view the table, it's just in Access I can't view it.
Any help would be appreciated.
Check the design of "pr_earn", possibly is different from the design of the table you were using .
The design is not automatically updated in MSAccess. An alternative is to remove and link the table again.
best regards!

ODBC connection failure on Access 2013

Hi I am using Windows 7 and Access 2013. I am unable to link tables using Visual Fox Pro DB via Access after a windows update. I get the error message : ODBC connection failed. In order to fix this where should I start exploring? I went to windows regedit-> ODBC->ODBCINST.INI and I am not sure how to proceed from here.
To my opinion, you should start from "data sources(ODBC)",
then create a User DSN, by selecting the correct driver
Microsoft Visual FoxPro Driver.
Then you can setup all needed information to create a ODBC connection to your Foxpro database. (I don't have FoxPro as it's not used in my company), but we do the same between MS Access and Oracle.
Once set, you can open your MS Access database and create linked tables towards your FoxPro database via the ODBC DSN just created.
good luck !

MS-Access 2003 CurrentDb.TableDefs("tablename").Connect Database is nothing

So I've inherited this project at work that runs in Access 2003, we're upgrading to a newer version of windows (from Windows Server to Windows 7).
It uses a DSN to connect to our MySQL database, however, Access isn't seeing the database name from the DSN settings.
I already determined the ODBC error, which is as follows:
[MySQL][ODBC 5.1 Driver][mysqld-5.6.22-log]No database selected
When I run ?myDB.TableDefs("tblusers").Connect in the immediate window, I get this response:
ODBC;DSN=bnr-rolodex;DATABASE=
I've been wracking my brain for a day or two now and was wondering if anyone else had run into this.
Thanks!
Edit: I should also note that ?CurrentDb.Connect returns blank and highlighting over it has a tooltip saying "Nothing = Nothing"
AVG solved my question in the comments. The DSN was already set up, but I wound up deleting it
I rebooted after, launched the application, kicked off the Linked Table Manager with this command in the immediate window in VB:
Application.Run "acwztool.att_Entry"
I readded the DSN from there, restarted again and fired access back up and it connected sucessfully! Thanks!

Connecting to remote mySQL via Excel VBA

Likely a dumb question but brain isn't piecing this together---
tl;dr: My main question is how do I choose the right parameters for my connection string? How do I determine what my driver should be? Provider? Option? Where do I find a list of acceptable parameters? How do I choose between ADO and OLE?
Objective: to connect to a hosted mySQL db of which I am admin.
Problem: creating a successful connection string / choosing the right parameters.
I'm new to referencing remote databases. Been looking all day today and yesterday; there are tons of articles and posts out there but nothing is working for me--I'm just trying to replicate what I see being done when I need to just design the string properly, but I don't know where to start.
I've tried using ActiveX Data Objects 2.7, 2.8 and 6.1 libraries. Also tried using OLE DB Simple Provider 1.5 Library. Below tests are using ADO 6.1.
Tried these connection strings:
DRIVER={MySQL ODBC 5.3 Unicode Driver};SERVER=ipaddress;PROVIDER=SQLOLEDB;DATABASE=xxx;UID=xxx;PWD=xxx;
---Error: waits ~30 seconds, times out and says Invalid Connection String Attribute
DRIVER={MySQL ODBC 5.3 Unicode Driver};SERVER=ipaddress;PROVIDER=Microsoft.Jet.OLEDB.4.0;DATABASE=db_name;USER=xxx;PASSWORD=xxx;
---Error: immediately errors and says cannot find installable ISAM
SERVER=ipaddress;PROVIDER=SQLOLEDB;DATABASE=xxx;UID=xxx;PWD=xxx;
---Error: waits ~30 seconds, times out and says SQL Database does not exist or access denied
I'm sure i've added the correct user with password and permissions. I haven't done anything with DSN.
I'm on win8.1 x64 using Excel 2013. Any advice is much appreciated!!

MS Access 2000 to MS Access 2007 migration

I have application in MS Access 2000.
It is connected to Oracle 9.2.06 database.
I have to migrate the application to MS Access 2007 and Oracle 11G.
I've created a blank .accdb file and imported all the objects from MS Access 2000 (.mdb) file, except the linked tables
While Linking MS Access 2007 with Oracle 11G database tables, i'm getting an error saying
"ODBC--call failed"
I've checked for Machine DSN, System DSN and its configured well alongwith ODBC Drivers.
Also, when i launch the application i'm getting an error as below:
"Error while connecting to '%Oracle database SID%'"
Could you please help me to resolve this issue.
Have you re-created all your ODBC links on your computer (in Administrator panel)? The ODBC is going to be different from Oracle 9.2 to 11.
you may need to import and reference libraries being used - check the Visual Basic Editor and confirm that all applicable libraries have been brought in.
The previously linked tables may have the credentials saved, or may not - you will have to check the properties of the linked table.