From: | <me(at)alternize(dot)com> |
---|---|
To: | Hélder M(dot) Vieira <hmv(at)mail(dot)telepac(dot)pt>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: 8.1.1.0, VB6, RDO, rdoResultset.RowCount |
Date: | 2005-11-10 01:16:22 |
Message-ID: | 0d5901c5e594$5eb44480$0201a8c0@iwing |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
hi there
this was discussed earlier today i think...
the recordset has an EOF (end of file) flag. if rs.EOF equals False, then
there are rows in the resultset.
cheers,
thomas
----- Original Message -----
From: "Hélder M. Vieira" <hmv(at)mail(dot)telepac(dot)pt>
To: <pgsql-odbc(at)postgresql(dot)org>
Sent: Thursday, November 10, 2005 2:06 AM
Subject: [ODBC] 8.1.1.0, VB6, RDO, rdoResultset.RowCount
> Hi.
>
>
> I noticed a difference in behaviour in 8.1.1.0, related with the RowCount
> property in RDO resultsets in VB6.
> In version 7xxx, for some specific purposes, I used to open a resultset
> and immediatly check RowCount.
> For non-empty resultsets, at this point in time RowCount would be
> innacurate but NOT EQUAL to 0, and based on this first evaluation I would
> proceed to the next step, either assuming an empty set or forcing a move
> to the last row to obtain a precise RowCount.
> In version 8.1.1.0, RowCount always seems to be EQUAL to 0, unless I force
> a move to the last row.
> At this point, my problem is that I don't know which is the right
> behaviour... Should I assume that in this and later versions of the driver
> RowCount will always be EQUAL to 0 before visiting the last row ?
>
>
> Thanks in advance.
>
>
> Helder M. Vieira
>
>
>
>
>
>
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
From | Date | Subject | |
---|---|---|---|
Next Message | Hélder M. Vieira | 2005-11-10 02:16:48 | Re: 8.1.1.0, VB6, RDO, rdoResultset.RowCount |
Previous Message | Andreas | 2005-11-10 01:09:34 | Re: How remove stale DSN ? |