From: | Ludek Finstrle <luf(at)pzkagis(dot)cz> |
---|---|
To: | Andrus <eetasoft(at)online(dot)ee> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error |
Date: | 2005-12-12 19:35:46 |
Message-ID: | 20051212193546.GA13184@soptik.pzkagis.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> > > I think I see the problem. I have some solutions in my mind but
> > > I have time in the evening at first.
> >
> > Thank you.
> > If you need I can try to create repro for this.
>
> It would be nice. I think I don't need it. But test is test and it's
> better to test the solution.
> So If you have time for it, I want it :-)
>
> The problem is reproducible this way:
> 1) bind X params
> 2) call ExecDirect - it fails (error, e.g. non-existing column)
Please, could you create two programs? One fails in this step
(return error) and one doesn't fail?
It could be interesting where it differs.
> 3) call SQLCancel
> 4) bind Y params (where Y < X)
> 5) call ExecDirect - this may return SQL_SUCCESS but it returns
> SQL_NEED_DATA right now
I'm not sure if my solution is good idea. I don't see the difference
between failure and non-failure process.
Thanks a lot
Luf
From | Date | Subject | |
---|---|---|---|
Next Message | Filip Wuytack | 2005-12-13 09:29:47 | Out of memory troubles with version 8.01.01.02 |
Previous Message | Ludek Finstrle | 2005-12-12 17:37:32 | Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error |