From: Rick on
If I need to move down x number of records Is there some easy way to
to do it other than

movenext
movenext
a bunch of times or create a loop?

I was hoping for something like Movenext(6)

Thanks, Rick
From: Tom van Stiphout on
On Tue, 1 Jun 2010 07:36:15 -0700 (PDT), Rick <rickhubner(a)gmail.com>
wrote:

You could write a procedure:
sub MoveNextMany(byval intHowMany as integer)
dim i as integer
for i = 1 to abs(intHowMany)
if intHowMany > 0 then
MoveNext
else
MovePrevious
end if
next i
end sub

Maybe better is to use the Bookmark technique. You can google or bing
for this. Keywords: recordsetclone, bookmark.

-Tom.
Microsoft Access MVP


>If I need to move down x number of records Is there some easy way to
>to do it other than
>
>movenext
>movenext
>a bunch of times or create a loop?
>
>I was hoping for something like Movenext(6)
>
>Thanks, Rick
From: Linq Adams via AccessMonster.com on
In other words, no! You have to either code

movenext
movenext

a bunch of times or create a loop.

You can follow Tom's advice and write a sub ***using a loop*** which will
make it easy to call it from different places, but you still have to write a
loop!

There is no native Access function for this, such as Movenext(6), which
appears to be your question.

--
There's ALWAYS more than one way to skin a cat!

Answers/posts based on Access 2000/2003

Message posted via http://www.accessmonster.com

From: KARL DEWEY on
What about using - GoToRecord
Arguments - Record - Next
- Offset - your value of records?

--
Build a little, test a little.


"Linq Adams via AccessMonster.com" wrote:

> In other words, no! You have to either code
>
> movenext
> movenext
>
> a bunch of times or create a loop.
>
> You can follow Tom's advice and write a sub ***using a loop*** which will
> make it easy to call it from different places, but you still have to write a
> loop!
>
> There is no native Access function for this, such as Movenext(6), which
> appears to be your question.
>
> --
> There's ALWAYS more than one way to skin a cat!
>
> Answers/posts based on Access 2000/2003
>
> Message posted via http://www.accessmonster.com
>
> .
>