"Torsten Bergmann" <[email protected]> writes: >>But it does not declare anything which is needed e.g for >>understanding SQLDouble and the like. > > Because FFI is a general callout mechanism for native APIs > and the ODBC package is just implemented on top of it. You are right, but it does not declare the handling of pointer or I have not understand it. > Just by looking at the code, maybe > - #initializeDataTypes has a wrong definition > - maybe the ODBCConstants definition is wrong > - maybe #initializeResultSet:number: has a problem Well I did exactly what you suggested and the problem is very likely in here: checkSQLReturn: (ODBCLibrary default sqlDescribeCol: resultSetHandle columnNumber: number columnName: columnName bufferLength: BUFFERSIZE nameLength: nameLenght dataType: columDataType columnSize: columnSize decimalDigits: decimalDigits nullable: columnNullable)
The problem here is that columnSize gives 53 with Access 2003. and this surely is wrong it may even be a problem in Access for ages because I found a hotfix for it for Access 2007 http://www.everythingaccess.com/tutorials.asp?ID=The-lowdown-on-Access-2007 I guess this may explain my problem. Anyway I'm not sure about it. So to me it seems this is a problem in the ODBC Driver vor Access, but I could not imagine that no-one ever have treated Doubles while trying to access MS Access with Pharo. > >>Sorry, does that mean the name I gave to the Data source must be placed >>in host? > > Yes, that worked for me. "host" is a bit misleading - for an > SQLite connection it can be the local path, for ODBC its the DSN name > for a network database it is the hostname or IP address. Sorry having a Database name in host is all but obvious. Regards Friedrich
