-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ODBC and geodatabase access fails on windows 7 64 bits #20256
Comments
Author Name: Jürgen Fischer (@jef-n) see also "GDAL !#5594":http://trac.osgeo.org/gdal/ticket/5594 |
Author Name: Jürgen Fischer (@jef-n) I can open the mdb attached to #17462 using following in the @qgis.bat@:
Apparently OGR's @odbc@ driver takes precedence over the @pgeo@ driver and has the same problems as the @pgeo@ driver w/o @PGEO_DRIVER_TEMPLATE@, which it obviously doesn't use. edit: quotes removed |
Author Name: Regis Haubourg (@haubourg) Jürgen Fischer wrote:
That solution doesn't work here.. |
Author Name: Jürgen Fischer (@jef-n) Regis Haubourg wrote:
Odd. I must have added the quotes after I tried. Without the quotes it works here... |
Author Name: Regis Haubourg (@haubourg) Jürgen Fischer wrote:
With or without quotes, I still don't get it to work. I double checked that env var were correctly seen from qgis session. |
Author Name: Jürgen Fischer (@jef-n) Regis Haubourg wrote:
Just to confirm: you have the "64bit Microsoft Access driver":http://www.microsoft.com/en-us/download/details.aspx?id=13255 installed? |
Author Name: Regis Haubourg (@haubourg) Ouch, you get it! So, I see few solutions:
I'm a bit puzzled.. Interoperability looses a lot there.. |
Author Name: Jürgen Fischer (@jef-n) Regis Haubourg wrote:
Whether your operating system is 32bit or 64bit doesn't really matter. You can use 32bit QGIS on both. But you need a 32bit ODBC driver for it (and that might still advertise itself without *.accdb and you don't need @PGEO_DRIVER_TEMPLATE@). If you want 64bit QGIS you need a 64bit OS and a 64bit ODBC driver - and AFAIK there is no 64bit Access ODBC driver without *.accdb so you always need @PGEO_DRIVER_TEMPLATE@ (and in turn OGR_SKIP) too. As you don't need to configure a data source manually for GDAL/QGIS you don't need to be careful to use the @odbcad32.exe@ from @%WINDIR%\SYSWOW64@ on a 64bit systems to configure 32bit data sources either (but you can use it to verify which 32bit ODBC drivers you have).
On Unix GDAL uses unixodbc and mdbtools - I guess that could be stripped down to work on Windows. But I don't think it's worth the effort - even ESRI switched to something else, didn't they? |
Author Name: Regis Haubourg (@haubourg) Hi, |
Author Name: Regis Haubourg (@haubourg) Shall I close the ticket ? Any work remaining on OGR side? |
Author Name: Regis Haubourg (@haubourg) Jürgen Fischer wrote:
Does that mean it's not possible to open classical mdb files (non geodatabases)? I couldn't open any, when Geodb are allright
Well, users seem to keep working with it (not here, but we rely on them) because they have a Access relational db GUI , when other formats do not allow such things.. |
Author Name: Regis Haubourg (@haubourg) Regis Haubourg wrote:
EDIT: This tips breaks office 32 bit access install. DO NOT FOLLOW THAT ! |
Author Name: Jürgen Fischer (@jef-n) Addressed in GDAL trunk
|
Author Name: Jürgen Fischer (@jef-n)
|
Fixes qgis#20256 (cherry picked from commit 3961fa2)
Author Name: Regis Haubourg (@haubourg)
Original Redmine Issue: 12054
Affected QGIS version: 2.6.0
Redmine category:data_provider
Hi,
ODBC access and geodatabase access that is internally based on ODBC fails on windows 64 bits platforms,.
This is related to two differents implementations of ODBC manager, one for 32 bits, the other for 64 bits. I guess QGIS or GDAL uses always 32 bit executable.
See this "article":https://robertoschiabel.wordpress.com/2008/02/28/windows-x64-32bit-odbc-vs-64bit-odbc/
This ticket is probably concerning GDAL upstream. Can anyone confirm? If true, I will file a ticket there.
Related issue(s): #17462 (duplicates), #21945 (duplicates), #26125 (relates)
Redmine related issue(s): 8752, 13927, 18234
The text was updated successfully, but these errors were encountered: