psqlODBC 09.00.0101 issue with adodb and adLockOptimistic

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.

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

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: psqlODBC 09.00.0101 issue with adodb and adLockOptimistic

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


--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: psqlODBC 09.00.0101 issue with adodb and adLockOptimistic

Hi,

I tried the unicode-binary from your site and replaced the corresponding
files within my current 8.4.0200 folder with the new 9.0.0102 dlls. The
broken ADODB code works now as far as I see in a hurry. :)

Will you build a new msi-distribution?


Thanks for the fast response.
:)


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
>
>


--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

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
>
>


--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: psqlODBC 09.00.0101 issue with adodb and adLockOptimistic

Hi,

(2010/10/24 12:35), Andreas wrote:
> Hi,
> me again.
>
> I've found an issue with 09.00.0102.
> Access shows just 101 records from linked tables and stored passthrough
> queries.

Thanks for the report.
I can't reproduce such a case here.
Could you send me directly the Mylog output?

regards,
Hiroshi Inoue

> 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. :)

--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: psqlODBC 09.00.0101 issue with adodb and adLockOptimistic

Am 24.10.2010 13:05, schrieb Hiroshi Inoue:
> (2010/10/24 12:35), Andreas wrote:
>> I've found an issue with 09.00.0102.
>> Access shows just 101 records from linked tables and stored passthrough
>> queries.
>
> Thanks for the report.
> I can't reproduce such a case here.
> Could you send me directly the Mylog output?

How would I get this mylog output if I can't switch it on in the DNS.
Which connect-string option would do this?



--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Re: psqlODBC 09.00.0101 issue with adodb and adLockOptimistic

(2010/10/25 5:38), Andreas wrote:
> Am 24.10.2010 13:05, schrieb Hiroshi Inoue:
>> (2010/10/24 12:35), Andreas wrote:
>>> I've found an issue with 09.00.0102.
>>> Access shows just 101 records from linked tables and stored passthrough
>>> queries.
>>
>> Thanks for the report.
>> I can't reproduce such a case here.
>> Could you send me directly the Mylog output?
>
> How would I get this mylog output if I can't switch it on in the DNS.
> Which connect-string option would do this?

The option is
Debug=1
..

regards,
Hiroshi Inoue




--
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc