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

Tech-Archive recommends: Speed Up your PC by fixing your registry

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

Date: Wed, 25 Aug 2004 21:32:44 +0300

david epsom dot com dot au wrote:
> DAO360 help: "If you delete the last remaining record in the Recordset
> object, the BOF and EOF properties may remain False until you attempt
> to reposition the current record."

Oh, that's quite specific. If the DAO360 help is correct the help files for
ADO and DAO about Requery should be changed.

> I have some unresolved issues with requery/BOF/EOF, but in your case
> doesn't it look more like a latency problem between your form
> recordset and your project connection, rather than a failure of
> requery/BOF/EOF ???

If you run the respective VBA code in the test database, wait a minute and
then close the form you still get a runtime error. Is that what you mean by
latency problem?
Do you have a link to sample code explaining some of your unresolved issues
with requery/BOF/EOF in detail? If I see some code I might be able to answer
the question if my problem belongs to the same category or is a new one.

Boris

> [...]

Relevant Pages