Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error - Mailing list pgsql-odbc

From Andrus
Subject Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
Date
Msg-id dnrkko$2vdh$1@news.hub.org
Whole thread Raw
In response to Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error  ("Dave Page" <dpage@vale-housing.co.uk>)
Responses Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error  (Ludek Finstrle <luf@pzkagis.cz>)
List pgsql-odbc
>> 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
> all possible!

>> I think bind parameters can't be destroyed in SQLCancel.
>
> Yeah, after re-reading it, I think you're right. :-(

Any other ODBC driver works with Visual FoxPro without needing special
configuration.
Can we find a way to implement this in pgodbc also ?

Andrus.



pgsql-odbc by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Next development steps?