Re: BOF or EOF error -MSAccess Fixed
- From: "Mike Martin" <mikem@xxxxxxx>
- Date: Wed, 25 Jan 2006 02:13:27 -0700
It seems to be fixed for the moment, not that I understand it. The problem
does not occurr when the recordcount is 0, so this seems to have fixed the
problem. I guess it doesn't want me to close the query when eof is true.
if q1.recordcount > 0 then
q1.first.
q1.close;
I did see a slight difference in MSAccess driver versions under ODBC,
between my Win2K and WinXP computers. I don't don't know if ODBC has
anything to do with ADO.
"Mike Martin" <mikem@xxxxxxx> wrote in message
news:43d72586@xxxxxxxxxxxxxxxxxxxxxxxxx
> On Windows XP computers, my application receives this eOleException when
> when performing MyADOQuery.close (or .free). This does not happen on Win2K
> computers.
>
> Either BOF or EOF is true, or the current record has been deleted.
>
> It's a simple select query, but eof is definitely true. The error occurs
> after looping through the rows.
>
>
.
- Follow-Ups:
- Re: BOF or EOF error -MSAccess Fixed
- From: Steve Zimmelman
- Re: BOF or EOF error -MSAccess Fixed
- References:
- BOF or EOF error -MSAccess
- From: Mike Martin
- BOF or EOF error -MSAccess
- Prev by Date: Re: ADO patch for D5? EOF BOF error.
- Next by Date: Re: ADO patch for D5? EOF BOF error.
- Previous by thread: BOF or EOF error -MSAccess
- Next by thread: Re: BOF or EOF error -MSAccess Fixed
- Index(es):
Relevant Pages
|