Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error

Поиск
Список
Период
Сортировка
От Ludek Finstrle
Тема Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
Дата
Msg-id 20051212173732.GA12319@soptik.pzkagis.cz
обсуждение исходный текст
Ответ на Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error  ("Andrus" <eetasoft@online.ee>)
Ответы Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error  (Ludek Finstrle <luf@pzkagis.cz>)
Список 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)
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 know you're working with FoxPro. This is mainly for other developers.
You can take an idea how to create minimal repro ...

It doesn't care if the test fail with C000005. Mylog has to contain
second ExecDirect which returning SQL_NEED_DATA.

Thanks

Luf

В списке pgsql-odbc по дате отправления:

Предыдущее
От: "Andrus"
Дата:
Сообщение: Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error
Следующее
От: Ludek Finstrle
Дата:
Сообщение: Re: Access violation C5 error on Visual FoxPro SQLEXEC() call after error