Re: [q-lang-users] ODBC connection with MS Access

[<jir...@bl...>]

Albert Graef napsal(a):
...
...
...
> AFAICT, there's nothing wrong in that code. Could it be that it's a
> binary incompatibility (i.e., maybe you're running a different ODBC
> version with a different ABI than that what I compiled the ODBC module
> against)? What does odbc_info DB say on your system?

==> odbc_info DB
("EUROSTAT","D:\\working\\EB\\tools_pro_EUROSTAT\\DB_EUROSTAT","ACCESS","04.00.0000","odbcjt32.dll","04.00.6304","03.51","03.52.0000")
...
...
...
> All operations, including sql_exec, check the return value of each and
> every ODBC call where an error can arise, and, if that return value
> indicates an error, the operation will bail out and return the error in
> the form 'odbc_error MSG STATE' where MSG is the error message and state
> is the SQL_ERROR state. At least that's how it's supposed to be, if that
> doesn't happen then it's a bug. But at the call in question, it clearly
> checks for an error condition, so it appears that SQLBindParameter()
> doesn't return one.

It should return an error condition as seen from the ODBC log:

Q2.tmp ODBC_MS_ e24-e28	EXIT  SQLBindParameter  with return code -1
(SQL_ERROR)
		HSTMT               00E22240
		UWORD                        7
		SWORD                        1 <SQL_PARAM_INPUT>
		SWORD                       99 <SQL_C_DEFAULT>
		SWORD                        1 <SQL_CHAR>
		SQLULEN                    0
		SWORD                        0
		PTR                0x00000000
		SQLLEN                     0
		SQLLEN *            0x003EE28C

		DIAG [HY104] [Microsoft][Ovladač ODBC pro Microsoft Access]Neplatná
hodnota přesnosti.  (98)
// means "Invalid value of precision"


> Maybe you can work around the error for now

I already did.

, and send me a minimal
> script, dataset and Access database that reproduces the bug, along with
> detailed instructions on how to reproduce it (baby steps and all that
> ;-). (Or enter the bug report at the q-lang.sf.net bug tracker, if you
> prefer that.) Then I'll have a look at it asap.

A zip file is enclosed. The procedure is described in the script.

Since the conference does not accept zip files, I renamed it to xxx. To 
unpack rename it back to zip.


Many thanks,

Jiri