AbsolutePosition is inferior to bookmark, so I can't recommend that
approach.
Instead of using a For...Next loop with a counter, loop until EOF. This will
avoid the invalid bookmark message you received when you moved past the end
of the recordset.
Here's an example:
http://allenbrowne.com/func-DAO.html#DAORecordsetExample
There are other things that could fail, e.g. the MoveFirst will fail if
there are no records. More info in:
Traps: Working with Recordsets - 10 common mistakes
at:
http://allenbrowne.com/ser-29.html

Signature
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
> I've found an alternative that avoids the problem described in my original
> post. Instead of using the Bookmark property and a comparison of bookmark
[quoted text clipped - 43 lines]
>>
>> Do Until .CompareBookmarks(.Bookmark, varBookmark) = adCompareEqual
Jay - 28 Mar 2008 08:23 GMT
Thanks for the response and the information leads, Allen. Additional
research confirms your opening statement; the bookmark appears to be more
robust and the method of choice in most situations. I'll consider it first
whenever faced with having to drop a "breadcrumb" in a recordset.
Thanks again,
Jay
> AbsolutePosition is inferior to bookmark, so I can't recommend that
> approach.
[quoted text clipped - 59 lines]
> >>
> >> Do Until .CompareBookmarks(.Bookmark, varBookmark) = adCompareEqual