> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Ludek Finstrle
> Sent: 14 December 2005 01:11
> To: Andrus Moor
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Access violation C5 error on Visual
> FoxPro SQLEXEC() call after error
> Sun, Dec 11, 2005 at 11:50:33AM +0200, Andrus Moor napsal(a):
> > Driver: psqlodbc-8_01_0104.zip ( I think)
> > Platform: Visual FoxPro 09.00.0000.3504 for Windows [Nov 4
> 2005 17:39:44]
> > Any idea how to fix this ?
> I tried to fix it but this seems to me as VFP bad behaviour. I'm
> againist add this code to official release unless we make new option
> in configure DSN dialog.
We need to be reducing the number of options, not increasing them if at
> Dave I propose to rollback your patch for the first Andrus's problem
> as it breaks ODBC specification (if I understand this well):
> | After SQLExecute or SQLExecDirect returns SQL_NEED_DATA and before
> | data has been sent for all data-at-execution parameters,
> | an application can call SQLCancel to cancel the statement execution.
> | After the statement has been canceled, the application can call
> | SQLExecute or SQLExecDirect again.
> I think bind parameters can't be destroyed in SQLCancel.
Yeah, after re-reading it, I think you're right. :-(
pgsql-odbc by date
|Next:||From: Andrus||Date: 2005-12-15 10:47:27|
|Subject: Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error|
|Previous:||From: Dave Page||Date: 2005-12-15 09:11:39|
|Subject: Re: Next development steps?|