🚀 go-pugleaf

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