| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | Garner Chung <garner(at)nuws(dot)com> |
| Cc: | pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: use declare/fetch |
| Date: | 2006-10-20 21:39:38 |
| Message-ID: | 4539421A.30909@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Garner Chung wrote:
> We're experimenting with the "use declare/fetch" setting in our MS
> Access/DAO - PG 8.1 environment. We're using the psqlODBC snapshot
> driver version, 8.02.01.03.
>
> However, we're experiencing a problem. With the "use declare/fetch"
> setting on we get an error on the (cache size - 49)th call to a dao
> recordset's MoveNext method. So with our current cache size setting of
> 500, the 451st call to MoveNext generates an ODBC error. With the cache
> size set to 100, the 51st call to MoveNext fails. See below for the
> relevant COMM log entries.
Could you send me directly the Mylog output ?
regards,
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | noreply | 2006-10-21 03:41:56 | [ psqlodbc-Bugs-1000759 ] SQLGetInfo(SQL_NULL_COLLATION) returns SQL_NC_END instead of SQL_NC_HIGH |
| Previous Message | Garner Chung | 2006-10-20 18:49:39 | use declare/fetch |