Thread View: borland.public.cppbuilder.database.ado
3 messages
3 total messages
Started by J. R. Antley
Sun, 01 Apr 2001 23:51
Still seeing "Either BOF or EOF is true or the current record has been deleted..." - Workaround!
Author: J. R. Antley
Date: Sun, 01 Apr 2001 23:51
Date: Sun, 01 Apr 2001 23:51
46 lines
2453 bytes
2453 bytes
Hi NG, I have gotten and installed BCB ADOExpressUpdate 1, but I still see this exception on my Windows 2000 Pro machine [which has MDAC 2.6]. What I'm trying to do: I'm using MSAccess 97 to create this table [okay, this is a pseudo-table to demonstrate my problem]. My hypothetical table looks like: Host Info1 Info2 ----- ------ ------ aaaa dork 1 aaaa dork 2 aaaa dork 3 aaaa fuzz 99 Now I want to find and step through all the records with "aaaa" in my Host field, which is indexed and the current index in the table. Since Seek() doesn't work [why oh why isn't such a basic feature of indexed tables supported?], I use Locate to find the first instance of "aaaa", then FindNext() until EOF is true or the value of Host is not "aaaa". When I try the FindNext() from the last record in the table, it should return FALSE and set EOF to true. Instead it generates the exception "Either BOF or EOF is...". If I use Next() instead of FindNext, no exception is generated, but EOF is never set. Finally I tried MoveBy(1) and found that it will not generate the exception, nor will it set EOF, but it does return 0 when positioned on the last record in the table. So I have a workaround, but I'm concerned about how my application will work on various operating systems with various versions of MDAC. Is this consistent with what y'all have seen? I don't think this will do much to help those of you who are using SQL, but it might provide some insight as to how it is failing beneath the covers. Cheers, JR
Re: Still seeing "Either BOF or EOF is true or the current record has been deleted..." - Workaround!
Author: Peter Dragun
Date: Sun, 01 Apr 2001 23:17
Date: Sun, 01 Apr 2001 23:17
29 lines
1523 bytes
1523 bytes
Looking at your hypothetical table is Info2 your key field? If not, then the fact that your table has no key to reference to each record is most likely causing you the grief. So your table would be: ID Host Info1 Info2 --- ----- ------ ------ 1 aaaa dork 1 2 aaaa dork 2 18 aaaa dork 3 24 aaaa fuzz 99 > > I'm using MSAccess 97 to create this table [okay, this is a pseudo-table to > demonstrate my problem]. > > My hypothetical table looks like: > > Host Info1 Info2 > ----- ------ ------ > aaaa dork 1 > aaaa dork 2 > aaaa dork 3 > aaaa fuzz 99 >
Re: Still seeing "Either BOF or EOF is true or the current record has been deleted..." - Workaround!
Author: J. R. Antley
Date: Mon, 02 Apr 2001 08:16
Date: Mon, 02 Apr 2001 08:16
45 lines
1985 bytes
1985 bytes
Thanks for the response, Peter, I can see why you're interested. No, in my table, I have a HostIndex, which is just an index onf the Host Field. I also have a Primary Index defined, which is the combination of all three of my fields. AYAYK, could this be a problem? TIA, JR "Peter Dragun" <pdragun@home.com> wrote in message news:3ac7fd55$1_2@dnews... > Looking at your hypothetical table is Info2 your key field? If not, then > the fact that your table has no key to reference to each record is most > likely causing you the grief. > > So your table would be: > ID Host Info1 Info2 > --- ----- ------ ------ > 1 aaaa dork 1 > 2 aaaa dork 2 > 18 aaaa dork 3 > 24 aaaa fuzz 99 > > > > > > > > I'm using MSAccess 97 to create this table [okay, this is a pseudo-table > to > > demonstrate my problem]. > > > > My hypothetical table looks like: > > > > Host Info1 Info2 > > ----- ------ ------ > > aaaa dork 1 > > aaaa dork 2 > > aaaa dork 3 > > aaaa fuzz 99 > > > > >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads