How to avoid TADOQuery's EOF-BOF-error

Article View: borland.public.cppbuilder.database.ado

Article #5000

Back to borland.public.cppbuilder.database.ado Previous Next

#5000

From: JR
Date: Mon, 20 Aug 2001 06:36

11 lines
1360 bytes

"Either BOF or EOF is true or the current record has been deleted".

I know it could be solved with BCB and ADOExpress updates but I'm currently
using a trial version of BCB so the updates can't be installed.

As far as I know, the error happens when trying to close an empty dataset.
So I've been trying to insert a record into TADOQuery before closing it.
After calling TADOQuery->Insert( ), TADOQuery->IsEmpty( ) returns false but
TADOQuery->RecordCount is still 0 and the exception is thrown.

Any clues?

Technical Details

Message-ID: <3b80afc2_1@dnews>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!news.tele.dk!small.news.tele.dk!194.25.134.62!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!dnews

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10698b,f24c3aedc1e42da3,start
X-Google-Attributes: gid10698b,public
X-Google-ArrivalTime: 2001-08-19 23:38:39 PST
From: "JR" <jake78@mbnet.fi>
Newsgroups: borland.public.cppbuilder.database.ado
Subject: How to avoid TADOQuery's EOF-BOF-error
Date: Mon, 20 Aug 2001 09:36:28 +0300
Lines: 13
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2479.0006
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006
NNTP-Posting-Host: 195.197.246.42
Message-ID: <3b80afc2_1@dnews>
X-Trace: dnews 998289346 195.197.246.42 (19 Aug 2001 23:35:46 -0700)
Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!news.tele.dk!small.news.tele.dk!194.25.134.62!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!dnews