Re: [q-lang-users] ODBC connection with MS Access
Brought to you by:
agraef
From: Albert G. <Dr....@t-...> - 2008-01-24 01:11:14
|
Jir(í Spitz wrote: > The called sql_exec procedure is not further evaluated. You mean it doesn't even return an odbc_error term? That's weird. Ok, so obviously some ODBC function being called in sql_query returns an error code. If sql_exec doesn't give you an error code, then I guess you'll just have to compile your own version of the odbc module and insert some printf's into the function (it's at line 563 in odbc.c), so that you can find exactly where it fails. (Watch out for all places with return's and goto's.) > From curiosity I tried precisely the same scripts against the > PostgreSQL database and all imports went OK without any errors - both > short and long records. So it is obvious that this issue is specific to > the MS Access ODBC driver implementation. That's my guess, too. Unfortunately, I don't have Access on my Windows box and I'm really snowed under work, so I can't debug it myself right now. But if you can find in which ODBC call sql_query exactly fails, and with which error code (if any), then we might be able to figure it out. Albert -- Dr. Albert Gr"af Dept. of Music-Informatics, University of Mainz, Germany Email: Dr....@t-..., ag...@mu... WWW: http://www.musikinformatik.uni-mainz.de/ag |