Re: psqlODBC 09.00.0101 issue with adodb and adLockOptimistic

Hi,
me again.

I've found an issue with 09.00.0102.
Access shows just 101 records from linked tables and stored passthrough
queries.
After exchanging the 09.00.0102 dlls back to the old 8.4.200 it was all
again as expected.
So there is some interference of Access with the odbc driver that
introduce those limits.

I use dsn-less connections by the way.
Every tabledef-object stores the whole connection string.

Maybe tha helps.
Have a nice sunday. :)

Am 23.10.2010 15:46, schrieb Hiroshi Inoue:
> Hi Andreas,
>
> (2010/10/23 4:41), Andreas wrote:
>> Hi,
>>
>> PG 8.4.4 on WinXP
>>
>> I recently installed psqlODBC 09.00.0101 and now a piece of access-vba
>> doesn't work anymore.
>> It's just those few lines that open recordsets for writing within my
>> application.
>
> Thanks for the report.
> Could you please try the drivers on testing for 9.0.0102 at
> http://www.ne.jp/asahi/inocchichichi/entrance/psqlodbc/
> ?
>
> regards,
> Hiroshi Inoue
>
>> Dim rst As New ADODB.Recordset
>>
>> With rst
>> .CursorLocation = adUseServer
>> .CursorType = adOpenDynamic
>> .LockType = adLockOptimistic
>> .Open strSQL, gpgconn.objConn, , , adCmdText
>> end with
>>
>> It apeares there is an issue with adodb and adLockOptimistic now.
>> When I switch to adLockPessimistic it works a bit better.
>> Now I can add a new record as well as write some values then close the
>> recordset.
>> Shortly after I need to change some data in this record so I select the
>> previously new created record with it's primary key and now I can write
>> to it again.
>> As soon I call rst.update an error rises "not enough data in message
>> left"
>>
>> After downgrading to psqlODBC 08.04.0200 the stuff works again.
>>
>> Is this a bug or a new feature ?
>>
>>
>> Regards
>> Andreas
>
>