Re: Empty "If Me.Recordset Is Nothing Then" clause causes runtime error 3021 (Access 2003)

From: Boris (boris_at_gtemail.net)
Date: 08/23/04 

Date: Mon, 23 Aug 2004 19:18:44 +0300

david epsom dot com dot au wrote:
> cal.Requery is not the same as rest.Requery, (although you would
> not know it by just leafing through the help files). The query
> plan is cached, and unless it has changed (cal.recordsource =
> cal.recordsource), requerying the object may not generate a dao/ado
> requery.
>
>> calling Requery is "equivalent to calling the Close and Open
>> succession". When you browse to the documentation of Open (at
>
> Ok, so lets get this straight :~) The help file (that well
> known font of wisdom), says that requery is 'equivalant' to
> open, therefore it follows that MS should change Access 2003
> BOF/EOF behavior to match your expectations....
>
> I agree that this could be an improvement on the system implemented
> in Access 2, 95, 97, 2002, and XP, but I'm less than sanguine
> about making changes to code that works 'good enough'.

In our test database a call to Requery updates RecordCount to 0 but not BOF
and EOF to false. In my opinion this is a bug in Access and not in the help
file. Or is there any reasonable explanation why BOF and EOF should be true
if RecordCount is set to 0?

Boris

> [...]

Relevant Pages
Loading