I am trying to use odbc snowflake to pull excel queries in windows arm. The only office (excel) that I can download is 32 bit. When I download the 32 bit snowflake odbc driver odbc 32 manager will not see it. I also noticed that when I open the 32 bit odbc manager it says 64 bit on the top. Naturally I tried downloading the 64 bit snowflake driver I can see it in the odbc manager but it won’t work. Anyone successfully set up odbc in windows arm?
It definitely sounds like you are in the 64-bit Windows driver manager as least from the observations you noted. I don't know ARM at all, but does the OS have a 32-bit Windows driver manager? Here is my location for it by default in Windows 10:
C:\WINDOWS\syswow64\odbcad32.exe
Related
I have a VB6 legacy application that uses 32-bit ADO drivers to make a database connection using ODBC.
Now the customer has installed the 64-bit version of the database, and I am getting an error:
[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application
Error Source: Microsoft OLE DB Provider for ODBC Drivers
I checked the net but could not find 64-bit OLEDB drivers for Windows Server 2012. There was a link for Windows Server 2003.
Can someone confirm whether the drivers exist and post the link to download them? Thanks.
EDIT 1:
This question is different from: Migrating VB6 code to use 64-bit ODBC DSN
This question is more about download the 64 bit ODBC driver, whereas that question is about code changes.
EDIT 2:
Even if I find 64-bit drivers, my VB6 application is 32-bit. Can a 32-bit application use 64-bit drivers at all? Note that installing the 32-bit version of database is ruled out.
Your legacy VB6 application is a 32-bit OLE DB consumer. It therefore requires a 32-bit OLE DB Provider for ODBC Data Sources, and a 32-bit ODBC Driver, such as those from my employer or various other sources.
The VB6 app loads some libraries into shared memory, and all of these much match bitness -- the VB6 app, the OLE DB Provider it loads, and in this case, the ODBC driver that loads, and in some cases, other libraries that loads.
Communications then happen over (typically) the TCP/IP stack or other networking layers -- which don't have to agree in bitness -- between the client-side libraries (i.e., ODBC driver) and the server-side (i.e., DBMS).
It does not matter that the target DBMS nor that the application's host OS is now 64-bit.
I am trying to connect to oracle using excel macro. My connection string is as follows:
*"Driver={Microsoft ODBC for Oracle}; CONNECTSTRING=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))(CONNECT_DATA=(SID=edw))); uid=system; pwd=oracle;"*
OS : Windows Server 2008 R2 Enterprise
MS Office Professional Plus 2013
Could you please help me.
Thanks in advance!!!
The driver does not exist, try Driver={Oracle in OraDb11g_home1}
However, ODBC exist for 32 bit and 64 bit. Which ODBC Data Source Administrator did you start (they look the same)?
To launch 64-bit ODBC Administrator use %SystemRoot%\System32\odbcad32.exe
To launch 32-bit ODBC Administrator use %SystemRoot%\SysWOW64\odbcad32.exe
The architecture of ODBC driver must match the architecture of your client, I assume this is MS Office which is most likely the 32 bit version.
ODBC driver for Oracle can be provided by Microsoft (Driver={Microsoft ODBC for Oracle}) or by Oracle (Driver={Oracle in OraDb11g_home1}, driver name varies). 64-bit driver is provided only by Oracle, the Microsoft driver is deprecated.
NB, I never used CONNECTSTRING=..., try Server=... instead.
My notebook has Windows 8 64 bit, Microsoft office 2010 32 bit and Oracle DB 11gR2 64 bit installed. I have created DSN to access oracle databases via ODBC sources 64 bit. I want to obtain data from oracle database to Microsoft Excel or Access via ODBC (in excel -> Data - From other sources - from Microsoft query). But DSN name that I created earlier do not appear. What can I do?
If the Application that wants to Access an ODBC-Datasource is 32bit, you need to use the 32bit version of the ODBC-Driver.
In your case you use a 32bit Version of Microsoft Office to Access the Datasource, so you need to use the 32bit Version of the ODBC-Driver. Configure your DSN using
C:\Windows\SysWOW64\odbcad32.exe
and they will probably show up in the 32bit Version of Office.
I am developing an app in Delphi 2010 that needs to communicate with remote Oracle 11g database. Therefore I use the ADODB components.
Everything is fine, as far as I am working on my desktop that has Windows 7 32-bit installed.
Problems started when I tried to deploy the app on Windows 7 64-bit with 64-bit Oracle Client installed. Luckily installing 32-bit client helped.
Unfortunately now I have to install it on my notebook with Windows 8 64-bit. None of the clients is working. I have already tried installing 64-bit client, 32-bit client, reinstalling both of them, installing then by OUI and manually, but without success.
Did anyone encounter this problem yet and managed to solve it?
The problem is on .dll of connection of Delphi odbc. We has the same problems with C++Builder (Delphis Like). Odbc client .dll for oracle connections is developed only for 32 bits.
Unitl then we only can connect to server 64bits with client 32bits. 64 bits server and 64 bits clients dont work. Unless you find thirdpartner odbc component, who doesn't use a native odbc .dll. We tried to use SQLDirect, but doesn't work well in firsts versions.
Best Regards,
Diogo Maschio
I've installed Visual FoxPro driver from this link on my 64 Bit Windows 7 Home Premium OS and tried to register vfpoledb.dll using REGSVR32. I could able to register this dll but when run my application which accesses VFP database is throwing the following error:
System.InvalidOperationException: The 'VFPOLEDB.1' provider is not registered on the local machine.
The same application is working fine in 32 bit Windows 7 Home Premium OS without any issues. I have googled for 64 bit VFP driver and found out that there are no VFP drivers for 64 bit OS from this link. Kindly help me to resolve this issue.
I have found out that there is no 64 bit VFP Driver for 64 bit OS. All we have to do is to change the build option in project properties and set the Platform Target to X86 instead of Any CPU. Build the application for X86. Please refer to this for more details.
It's a bit late, but may help somebody else:) You can use Advantage OLE DB Provider for Windows 64-bit, which works like VFPOLEDB. Example in python:
conn = win32com.client.Dispatch('ADODB.Connection')
dsn = 'Provider=Advantage OLE DB Provider;Data Source=%s; ServerType=ADS_LOCAL_SERVER; TableType=ADS_VFP;' % folder
conn.Open(dsn)
cmd.CommandText = 'ALTER TABLE test ALTER COLUMN area NOT NULL'
cmd.Execute()
A blog post by Eric Selje, of Salty Dog Solutions, describes how to run the 32-bit drivers on 64-bit Windows. (You must set them up in the 32-bit ODBC Administrator.)
Visual FoxPro, a 32-bit application, runs just fine on 64-bit machines.
Visual FoxPro cannot use 64-bit ODBC drivers however.
You can use 32-bit ODBC drivers on 64-bit Windows, but you must set them up in the 32-bit ODBC Administrator. This is not the one that’s
going to come up if you go through Control Panel. To invoke it, run
C:\Windows\SysWow64\odbcad32.exe and add your DSNs there.
Do not just Start, Run, ODBCAd32.exe, as it will not bring up the right one.
The 32-bit drivers for SQL Server come with Windows 7 x64, so you don’t have to download them.