There is an ODBC problem with Visual Foxpro 9. According to a Visual FoxPro maillist:
Since VFP caches a common statement handle that it reuses, it has to call SQLFreeStmt(SQL_UNBIND) and SQLFreeStmt(SQL_RESET_PARAMS) to make sure the cached statement handle is in a cleared state before reusing it. VFP indeed calls these functions when all goes well, but when an error occurs in SQLExecuteDirect it just calls SQLCancel and then returns from SQLEXEC...... At least for me this is a bug in VFP, which is caused by the fact that it caches a common statement handle but doesn't reset it correctly when an error occurs.
A thread does exist for the problem on the pgsql-odbc list under Subject: Re: [ODBC] Access violation C5 error on Visual FoxPro SQLEXEC() call after error
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Margaret Gillon, IS Dept., Chromalloy Los Angeles, ext. 297
This e-mail message and any attachment(s) are for the sole use of the intended recipient(s) and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient(s), please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachment(s) to the original message.
