🚀 go-pugleaf

Hi Paul,

This is a bug of ADO Express.
There is a patch for ADO Express in CodeCentral  that fixses this one and
some other
bugs.

Ivan



"Paul Machiaverna" <machiave@i-stat.com> wrote in message
news:908fug$apf7@bornews.inprise.com...
> In testing the performance of Borland ADOExpress for C++ Builder 5, I
wrote
> a simple test application.
>
> An ADO object point is declared:
>
> TADOQuery* iptQuery;
>
> After it is created and the connection to the database is made, the
> following code is executed:
>
> try
> {
>     // Perform the query.
>     iptQuery->Close();
>     iptQuery->SQL->Clear();
>     iptQuery->SQL->Add( "SELECT KeyValue FROM TestRecord" );
>     iptQuery->Prepared = true;
>     iptQuery->Open();
>
>     // While there are records to process,
>     while ( !iptQuery->Eof )
>     {
>         // Get the data and display it.
>         liData = iptQuery->FieldByName( "KeyValue" )->AsInteger;
>         MemoDisplay->Lines->Add( IntToStr( liData ) );
>
>         // Go to the next record.
>         iptQuery->Next();
>     }
> }
> catch( Exception& E )
> {
>     ShowMessage( E.Message );
> }
>
> // Close the query.
> iptQuery->Close();
>
>
> This all works fine until it hits the last line (iptQuery->Close()).
That's
> when an exception is throw and it reports:
>
> "Either BOF or EOF is True, or the current record has been deleted.
> Requested operation requires a current record."
>
> Why does this happen?  Is there a way to suppress this?  Since I just want
> to simply close the query, I really don't want an exception thrown and
> displayed.
>
> Paul
>
>
>