is there some solution how to use 32/64 bit ODBC Microsoft dBase Driver on Windows without Office installed?
Thank you for response.
Jet drivers used to be installed with Windows until the recent Windows editions. You can download ACE drivers for free ( http://www.microsoft.com/en-us/download/details.aspx?id=13255 ) Here is an example of usage : How to read/write dBase III files using C#/.NET ODBC or OLE?
Related
OS: Microsoft Windows Server 2008 R2 Enterprise - 64-bit - En.Us
DBMS: Microsoft SQL Server 2008 R2 Standard - Windows - 64-bit - En.Us
ODBC Driver: Progress OpenEdge 10.2B - Windows - 32-bit - En.Us
I don't have the related ODBC Driver in 64-bit version.
Do I have options to connect, to the Progress Database, using Query, or Linked Server? If I have, what are my options?
Thank you all!!!
The Progress ODBC drivers can be downloaded from the Progress site. Log in with your ID on http://www.progress.com/esd/
Contact support if you can't find them.
There's also a product called "Pro2" replication that can "almost live" replicate from Progress to for instance SQL server if you have that demand. It might only be offered from 11.X and forward, I'm unsure about that.
https://www.progress.com/openedge/features/openedge-pro2/
If you were to download one of the 11x 64bit Client Access bundles, these will quite happily connect to a 32bit 10.2b database.
http://knowledgebase.progress.com/articles/Article/P88405
You do have options. Fundamentally, you can use our Multi-Tier ODBC Drivers for Progress (versions 6.x to 10.x) to connect a 64-Bit ODBC Compliant application to a 32-Bit Progress RDBMS. This 64-Bit client to 32-Bit server bridging is achieved as a result of the RDBMS-independent communications layer used by these drivers.
I am using Windows 7 (x64bit) Ultimate.
I have both ODBC32 and ODBC64 Managers that I can access via Start.
The default appears to be the ODBC64.
However I do not see MSDASQL -Microsoft OLEDB for ODBC listed.
I wonder if it exists. I see some references to 64Bit MSDASQL for Windows Server 2003.
The IBM 64bit for ODBC seems to work (I heard) but not tried.
Now I would like to know if any one knows the link for 64-bit MSDASQL for Windows 7. Microsoft seems to have deprecated MSDASQL and I am not sure of the status of this story.
These issues came up while setting up a linked server in SQL Server 2012 for SQL (SAP) SqlAnywhere server.
I am not sure how I missed. This link allows you to download the Microsoft Access Database Engine 2010 Redistributable
http://www.microsoft.com/en-us/download/details.aspx?id=13255
The details of this indicates both ODBC and OLEDB as copied from the Microsoft Web Site:
"This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2010 (*.mdb and .accdb) files and Microsoft Office Excel 2010 (.xls, *.xlsx, and *.xlsb) files to other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats. "
There is no MSDASQL x64 bit for Windows 7. There is one for Windows Server 2003. I finally was able to create a linked server in SQL Server 2012 Express using the SAOLEDB.16 from Sybase/SAP.
Although I replied myself that there is no MSDASQL(x64)based on some 'deprecated items' information I am still looking at it.
Here is a link to the same question on MSDN:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/3c715023-4322-4bc6-a2c8-64a873f87e46/can-someone-confirm-the-architecture-of-this-file-preferably-microsoft-guys?forum=sqldatabaseengine#db5ed4e2-2391-4062-b34d-1f1b11431e1e
I am using Toad for Oracle Xpert 10.1.1.8 on Win 7 64bit operating system. I have installed Oracle 11g 64bit client. I am getting this error: Cannot load OCI DLL: C:\oracle\product\11.1.0\oci.dll. I googled this error and found TOAD only runs on 32bit Oracle Client. Is there any way to run TOAD on 64bit Oracle Client?
As per the knowledge article on Quest Support base
Toad for Oracle versions prior to 11.6 cannot support a 64-bit Oracle
Client due to limitations in Delphi programming language used in some
of Toads components.
Versions 11.6 onwards are fully 64-bit compliant. There is now a
64-bit installer and 32-bit installer. Please note that you should
install a 64-bit Oracle client for the 64-bit Toad installation and a
32-bit Oracle Client for the 32-bit installation.
For 11.5 and below, a 32-bit Oracle client must be installed
Hi i have an application developed on XP with Text ODBC drivers. But when i deployed on Win 7 with office 2007, i have connection issues.
<add key="SQLConnection.TextConnectionString" value="Driver={Microsoft Text Driver (*.txt; *.csv)};Dbq=c:\Data\;Extensions=asc,csv,tab,txt;Persist Security Info=False" />
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
i have googled every solutions like installing the following
http://blogs.msdn.com/b/sqlblog/archive/2009/12/29/how-to-connect-to-file-based-data-sources-microsoft-access-microsoft-excel-and-text-files-from-a-64-bit-application.aspx
Microsoft Access Database Engine 2010 Redistributable (32-bit)
2007 Office System Driver: Data Connectivity Components
after all of those, in my datasources(ODBC), it still only shows "SQL native client/SQL server/SQL server native client"
in the C:\Windows\SysWOW64\odbcad32.exe
i can see all the x32 drivers, but how can i modify my connection strings to access 32-bit Microsoft Text Drivers or are there any alternative solutions?
Thanks
I'm pretty sure it'll work automatically (even on a 64-bit machine) as long as the executing process is 32-bit.
Try recompiling to target x86 specifically.
You need the 64-bit Microsoft Access Database Engine 2010 Redistributable
http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Then try
Microsoft Access Text Driver (*.txt, *.csv)
for the driver name.
AFAIK, all 64-bit ODBC drivers from the Microsoft Access Database Engine 2010 64-bit Redistributable have slightly changed their driver names, I guess to differentiate them from their 32-bit counterparts.
I had this exact problem and the recompiling to target x86 specifically worked! Note that in order to do this I had to specify the Target CPU in the advanced compiler setting dialog - Project Menu> Properties> Compile tab> Advanced Compile Options button.
Before finding this forum entry I did install the Microsoft Access Database Engine 2010 Redistributable (32-bit) but I don't know if that had any affect on this issue.
As mentioned above, when the executing process is 32-bit (in this case compiling against x86 makes the app 32-bit specific) the application will use the drivers from C:\Windows\SysWOW64\odbcad32.exe.
Thanks Cameron.
We were doing this from ASP.Net and got it working on Windows 2012 just by moving the one site into a separate app pool that had "32-bit Enabled" turned on in the advanced settings for the App Pool.
A lot of people seem desperate here, I want to offer a few solutions. But, first I want to highlight what a dated proprietary trash idea from the 90s this is.
Use Unix ODBC to host the text file from Linux which the docs (seem to) claim to support an implementation of the Microsoft text driver
A better option would be of course to import the CSV into PostgreSQL.
I would suggest just doing this with \COPY and dropping the notion of a CSV.
You can maintain the CSV with PostgreSQL acting as a server with the Foreign Data Wrapper (file_fdw).
If you don't want to run an RDBMS, the modern way would be to use SQLite. This is a great idea if you don't need the server/client model.
The ODBC->text interface is especially insane, because ODBC doesn't define configuration beyond connection (so I assume there are lots of assumptions there).
The 64 bits version of Windows Server does not came with the ODBC DBF Drivers by default.
Is there a way to get them?
What alternatives exist?
I'm reasonably certain that the FoxPro drivers can read DBF's very well. I used this driver on Vista 64-bit without any problems, so I suspect it will work with Server 2003 x64.
FoxPro Driver