🚀 go-pugleaf

"pfinster" <pfinster@altavista.co.uk> wrote in message
news:d0PI8.2$D%4.83@newreader.ukcore.bt.net...
> Hi
>
> I have an unsupported application that uses BDE Administrator 5.0
connecting
> to a Personal Oracle 8 database and has ODBC connections to Progress
> databases.
>
> When querying a table in the Oracle database via BDE the records are
> returned twice.  If I look at the table through the Oracle Navigator, the
> correct number of records exist and if I query the table using Oracle
> SQLPlus, the correct number of records are returned.
>
> It doesn't do this all the time and I have yet to determine a pattern,
> although I am told this is seen more frequently lately.
>
> I was grasping at straws by changing the ROWSET SIZE from 20 to 40, but it
> seems to have resolved the issue.  Why?  Can I always rely on this?  What
is
> the best solution?
>
> Regards
> Ken
>
>

I found the solution on the Borland Developer Network:

Oracle 8 problems introduced in BDE 5.1.1. - by Borland Developer Support
Staff



  Abstract:Setting ROWSET SIZE to 0 resolves the issues.
      Previous to BDE 5.1.1, setting ROWSET SIZE for an alias connected to
Oracle 8 did nothing. BDE 5.1.1 added this as a new feature as a performance
enhancement to improve the speed when many records are fetched.
      However, this new feature introduces 3 new problems:

        a.. When the number of rows returned from a TTable or TQuery matches
a multiple of the setting of ROWSET SIZE data will be displayed twice.
        b.. If the last row of a TTable or TQuery has fields which are blank
(NULL), the corresponding field in the first record will be blank as well.
This problem does not occur when using the Oracle 8.1.5 client (8i). When
using the Oracle 8.0.4 client R&D has determined this problem to be caused
by a bug in the Oracle 8.0.4 client. Therefore, ROWSET SIZE must be set to 0
when using the 8.0.4 client.
        c.. Getting a list of tables in SQL Explorer may result in the error
"Translate Error. Value out of Bounds.".
        The workaround for all of these problems at this time to set ROWSET
SIZE to 0.






----------------------------------------------------------------------------
----