Skip site navigation (1) Skip section navigation (2)

Re: adodb - absolutepage

From: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
To: Bjørn Ivar Katla <katla(at)bitmaker(dot)no>
Cc: "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: adodb - absolutepage
Date: 2010-10-28 13:02:12
Message-ID: 4CC97454.2040500@tpf.co.jp (view raw or flat)
Thread:
Lists: 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) on my 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 is done by use of the .absolutepage property of ADODB.Recordset object.   I set pagesize and when I open the recordset - the rs.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

In response to

Responses

pgsql-odbc by date

Next:From: Bjørn Ivar KatlaDate: 2010-10-28 13:42:07
Subject: Re: adodb - absolutepage
Previous:From: Bjørn Ivar KatlaDate: 2010-10-28 12:20:18
Subject: Re: adodb - absolutepage

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group