-
Notifications
You must be signed in to change notification settings - Fork 34
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
Connecting with HDBC-ODBC in Windows 7 #14
Comments
I'm not familiar with the ODBC setup on Windows, but does the following return nicely, or does it produce an error?
If it's an error, then I can only presume that your connection string isn't quite right. |
It gives same error after:
I also tried to give wrong DBQ and it returns |
Have you also tried following the instructions here: |
I have tried to do that and system does not let me install MDAC 2.8 with error. It seems Windows 7 uses WDAC (Windows Data access Component) instead of MDAC and it comes preinstalled and can not be downgraded to MDAC 2.8. |
I had the same problem and error message on 64 bit Windows 10, with 64 bit Microsoft Access Version 1908 (Build 11929.20254 Click-to-Run) and the Microsoft Access Database Engine 2016 Redistributable fix, and a This Stack Overflow answer by @derrickturk and his fork of |
@derrickturk has identified (derrickturk@99cbefb) that, in the case of the MS Access driver, the `BufferLength` argument of function `SQLGetInfo` cannot be ignored (set to 0), despite what is implied by the Microsoft documentation (https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlgetinfo-function?view=sql-server-2017). `InfoType` `SQL_TXN_CAPABLE` returns a `SQLUSMALLINT` value and the `BufferLength` must be set accordingly.
When trying to connect to data source in Windows 7 with HDBC-ODBC rising
SqlError {seState = "[]", seNativeError = -1, seErrorMsg = "sqlGetInfo SQL_TXN_CAPABLE: []"}
Using Haskell Platform 2013.2.0.0 and Microsoft Access Database Engine 2010 Redistributable are installed.
Sample code which i use:
The text was updated successfully, but these errors were encountered: