Active7 months ago
May 15, 2019 Download CsvJdbc - CSV file JDBC driver for free. A read-only JDBC driver for Java that uses Comma Separated Value (CSV) files as database tables. Ideal for writing data import programs and conversion programs.
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.
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
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:WindowsSysWOW64odbcad32.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
KiddoKiddo3,01244 gold badges4040 silver badges6666 bronze badges
5 Answers
I'm pretty sure it'll work automatically (even on a 64-bit machine) as long as the executing process is 32-bit.
![Csv Odbc Driver Csv Odbc Driver](/uploads/1/2/4/8/124898712/626427959.png)
Try recompiling to target x86 specifically.
CameronCameron71.6k1616 gold badges167167 silver badges206206 bronze badges
You need the 64-bit Microsoft Access Database Engine 2010 Redistributable
Then try
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.
jumpinjackiejumpinjackie1,13733 gold badges1414 silver badges2424 bronze badges
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:WindowsSysWOW64odbcad32.exe.
Thanks Cameron.
SteveSteve
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.
WillWill
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
).
- I would suggest just doing this with
- 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.
Tps Odbc Driver
The ODBC->text interface is especially insane, because ODBC doesn't define configuration beyond connection (so I assume there are lots of assumptions there).
Evan CarrollEvan Carroll39.5k2626 gold badges156156 silver badges269269 bronze badges