Re: adodb - absolutepage - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: adodb - absolutepage
Date
Msg-id 4CC97454.2040500@tpf.co.jp
Whole thread Raw
In response to Re: adodb - absolutepage  (Bjørn Ivar Katla <katla@bitmaker.no>)
Responses Re: adodb - absolutepage  (Bjørn Ivar Katla <katla@bitmaker.no>)
List pgsql-odbc
(2010/10/28 21:20), Bjørn Ivar Katla wrote:
> Here are the results.  Pagecount are correct ( pagesize set to 20, records: 28)
>
> rs.absolutepage : -1
> rs.pagecount: 2
> rs.cursortype: 3
> rs.locktype: 3
> rs.cusorlocation: 2

Doesn't rs.CursorLocation=2 mean adUseServer?

regards,
Hiroshi Inoue

> regards
> Bjørn Ivar Katla
>
>>
>> (2010/10/28 4:58), Bjørn Ivar Katla wrote:
>>> Hi,
>>>
>>> I am implementing PostgreSQL as a replacement for a ms sql server  web application and are using pgsqlodbc (8.4.2)
onmy windows IIS/.ASP against my 8.4 postgreSQL database on an ubuntu server. 
>>>
>>> Part of this applications is to enable users to search data and only have 20 records displayed on each page.  This
isdone by use of the .absolutepage property of ADODB.Recordset object.   I set pagesize and when I open the recordset -
thers.absolutepage is -1 
>>>
>>> Here is the parameters I set when opening the recordset.
>>>
>>> rs.CursorLocation = adUseClient
>>> rs.PageSize = 20
>>> rs.Open sql, sconn,1,3
>>
>> I see .absolutePage=1 here.
>>
>> Could you display .CursorType, .LockType or .CursorLocation after
>> opening the recordset?
>>
>> regards,
>> Hiroshi Inoue

pgsql-odbc by date:

Previous
From: Bjørn Ivar Katla
Date:
Subject: Re: adodb - absolutepage
Next
From: Bjørn Ivar Katla
Date:
Subject: Re: adodb - absolutepage