I have an MS Access 2003 DB that was created by a contractor who has now left. The DB uses linked tables and DAO to connect to an ORACLE backend. It used to work until we recently upgraded our ORACLE version from 10g to 11g. As part of the upgrade we had to update our rather out dated "Microsoft ODBC for ORACLE" driver to "Oracle in instantclient11_1" thats forms part of the ORACLE Instant Client.
When we run the VBA it returns error code 3151 and says "ODBC --connection to 'MYDB' failed. I did a bit of googling and found that code 3151 is a generic code. However sometimes this works and other times(80% of the time) it doesn't.
Its installed on an MS Xp SP3 32bit machine and the drivers are 32-bit. From The ODBC Manager when I run the test connection it is always successful and I can query the DB from within excel and using the "Import External data"
Any idea how I can resolve this?
Related
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 !
Somehow I'm having a lot of trouble establishing an ODBC connection to MySQL from within MSSQL Management Studio. I have 64-bit versions of MSSQL and MySQL ODBC connector installed.
The local MySQL database already has a DSN assigned to it. I've used this DSN with Excel in the past and had no problems.
Now, (in SQL Man. Studio) when I access:
'Tasks' -> 'Import Data' -> '.Net Framework Provider for ODBC'
I get a helpful form asking me to enter all the connection details even though I've already registed the DSN in 'Control Panel\Data Sources'.
So, after a brief 'wait, what?", I enter:
Dsn: My_Dsn
Driver: MySQL ODBC 5.2 ANSI Driver
... and get: ERROR [IM014] [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
#
PS.
I've also tried creating a linked MySQL server in MS Studio like so: http://www.sqlservercentral.com/Forums/Topic340912-146-1.aspx
and get:
'contains no columns that can be selected or the current user
does not have permissions on that object.'
In short: no access to MySQL from within MSSQL Studio whatsoever
Thanks in advance!
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.
I am using Windows7 and Microsoft office 2010 and mysql5. I want to connect Microsoft excel with my database mysql. I have installed all the drivers. I have created a data source as well. I am going step-by-step to connect, but at the end when i click on test connections, I receive this error message
Test connection failed because of error in intializing provider unspecified error.
You probably are not using the right ODBC driver.
Please check if you downloaded the one that matches your MySQL database. (not only version number, but especially if it is a 32-bit server or a 64-bit server).
I just installed SQL Server 2012 to test differences and make sure it is ok for my Work. I may not be a pro at SQL, but I don't see how to add a Link to Jet database on my server. I have imported Jet Databases, but when going thru the GUI to Link a JET Database I see no Provider for JET. I am running Access 2003 (I don't like the 2008+ GUI)
I searched an found nothing simular to my issue; at least nothing I understood. Nothing mentioned how to add Jet db Provider.
I ran a connection string to the Jet Database thru QA:
sp_addlinkedserver 'USGEScrub', 'Access', 'Microsoft.Jet.OLEDB.4.0',
'D:\Lead$\SupList\USGEScrub.mdb'
The connection string works till I try to access the data and then I get this the errorand of course if I click the links nothing shows up:
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
Cannot create an instance of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked
server "USGEScrub". (Microsoft SQL Server, Error: 7302)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2100&EvtSrc=MSSQLServer&EvtID=7302&LinkId=20476
download the 2010 Access database engine from Microsoft
Allow "InProcess"
Add linked server using the ACE OLEDB provider.
more details here
I had a similar problem and in my case it turned out to be related to the permissions on the %TEMP% folder for the account under which the SQL Server service was running. For more details see my answer here.
Sometimes this problems occurs in computers x64 with office x84 versions installed. Try this:
Install pasive OleDb Driver x64