do i NEED to use .movefirst immediately upon opening a recordset?

[MLH]

Here's a blurb cut from A97 HELP on BOF/EOF:
When you open a Recordset object that contains at least one record,
the first record is the current record and the BOF and EOF properties
are False; they remain False until you move beyond the beginning or
end of the Recordset object by using the MovePrevious or MoveNext
method, respectively.

From that HELP blurb, it would seem that the .MoveFirst in the lines
below is simply not needed. Would you agree? Am I incorrect?

Set rstRRs = .OpenRecordset( dbOpenSnapshot)
With rstRRs
If .BOF = True Then GoTo NoRecs
.MoveFirst
Do Until rstRRs.EOF
If Int(Now()) - !DateSigned < WaitTime Then GottaWait = True
...

I would like to take the .MoveFirst out if it is not needed.

[Rick Brandt]

MLH wrote:

Here's a blurb cut from A97 HELP on BOF/EOF:
When you open a Recordset object that contains at least one record,
the first record is the current record and the BOF and EOF properties
are False; they remain False until you move beyond the beginning or
end of the Recordset object by using the MovePrevious or MoveNext
method, respectively.

From that HELP blurb, it would seem that the .MoveFirst in the lines
below is simply not needed. Would you agree? Am I incorrect?

Set rstRRs = .OpenRecordset( dbOpenSnapshot)
With rstRRs
If .BOF = True Then GoTo NoRecs
.MoveFirst
Do Until rstRRs.EOF
If Int(Now()) - !DateSigned < WaitTime Then GottaWait = True
...

I would like to take the .MoveFirst out if it is not needed.

I've never used MoveFirst in a situation like that. You can get rid of it.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

[MLH]

I was hoping you'd say that.
Many thanks!

[Bob Quintal]

MLH <CR**@NorthStat e.net> wrote in
news:dd******** *************** *********@4ax.c om:

Here's a blurb cut from A97 HELP on BOF/EOF:
When you open a Recordset object that contains at least one
record, the first record is the current record and the BOF and
EOF properties are False; they remain False until you move
beyond the beginning or end of the Recordset object by using
the MovePrevious or MoveNext method, respectively.

From that HELP blurb, it would seem that the .MoveFirst in the
lines below is simply not needed. Would you agree? Am I
incorrect?

Set rstRRs = .OpenRecordset( dbOpenSnapshot)
With rstRRs
If .BOF = True Then GoTo NoRecs
.MoveFirst
Do Until rstRRs.EOF
If Int(Now()) - !DateSigned < WaitTime Then GottaWait =
True ...

I would like to take the .MoveFirst out if it is not needed.

Yes: the .Movefirst is useless. It will even raise an error if
the recordset type is dbOpenForwardOn ly
You may also be able to delete the IF .BOF statement if the
NoRecs:label immediately follows your do loop.

--
Bob Quintal

PA is y I've altered my email address.

[Tom van Stiphout]

On Sat, 20 May 2006 08:30:28 -0400, MLH <CR**@NorthStat e.net> wrote:

Since after opening a recordset the record pointer is already at the
first record (if at least 1 record), it is a no-op. As Bob points
out, it is even counter-productive in some situations.

-Tom.

Here's a blurb cut from A97 HELP on BOF/EOF:
When you open a Recordset object that contains at least one record,
the first record is the current record and the BOF and EOF properties
are False; they remain False until you move beyond the beginning or
end of the Recordset object by using the MovePrevious or MoveNext
method, respectively.

From that HELP blurb, it would seem that the .MoveFirst in the lines
below is simply not needed. Would you agree? Am I incorrect?

Set rstRRs = .OpenRecordset( dbOpenSnapshot)
With rstRRs
If .BOF = True Then GoTo NoRecs
.MoveFirst
Do Until rstRRs.EOF
If Int(Now()) - !DateSigned < WaitTime Then GottaWait = True
...

I would like to take the .MoveFirst out if it is not needed.

[David W. Fenton]

"Rick Brandt" <ri*********@ho tmail.com> wrote in
news:b%******** **********@news svr11.news.prod igy.com:

MLH wrote:

Here's a blurb cut from A97 HELP on BOF/EOF:
When you open a Recordset object that contains at least one
record, the first record is the current record and the BOF and
EOF properties are False; they remain False until you move beyond
the beginning or end of the Recordset object by using the
MovePrevious or MoveNext method, respectively.

From that HELP blurb, it would seem that the .MoveFirst in the
lines below is simply not needed. Would you agree? Am I
incorrect?

Set rstRRs = .OpenRecordset( dbOpenSnapshot)
With rstRRs
If .BOF = True Then GoTo NoRecs
.MoveFirst
Do Until rstRRs.EOF
If Int(Now()) - !DateSigned < WaitTime Then GottaWait = True
...

I would like to take the .MoveFirst out if it is not needed.

I've never used MoveFirst in a situation like that. You can get
rid of it.

I never use BOF/EOF to test for an empty recordset, but instead use
RecordCount = 0 (one test is more efficient than two).

But I always explicitly .MoveFirst simply because I don't like
depending on something happening over which I have no control. It
can't possibly be a performance problem since it's only going to
happen once per recordset, so I don't see the issue with doing
something explicitly that may be slightly redundant.

I simply don't like assuming that things will work the way they are
supposed in all situations.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Chirag Shukla]

MLH wrote:

Here's a blurb cut from A97 HELP on BOF/EOF:
When you open a Recordset object that contains at least one record,
the first record is the current record and the BOF and EOF properties
are False; they remain False until you move beyond the beginning or
end of the Recordset object by using the MovePrevious or MoveNext
method, respectively.

From that HELP blurb, it would seem that the .MoveFirst in the lines
below is simply not needed. Would you agree? Am I incorrect?

You are correct.
Chirag Shukla.

[Terry Kreft]

The .MoveFirst is less of a problem than the
If .BOF = True Then GoTo NoRecs

You should not use GoTo unless absolutely forced to, it creates spaghetti
code which can easily become very difficult to debug.

The .MoveFirst is not necessary. without it (and after removing the GoTo
line) your code becomes

Set rstRRs = .OpenRecordset( dbOpenSnapshot)
With rstRRs
Do Until .EOF
If Int(Now()) - !DateSigned < WaitTime Then GottaWait = True
Without knowing the rest of your code it's not possible to recommend how to
handle the situation where the recordset is empty.

--

Terry Kreft
"MLH" <CR**@NorthStat e.net> wrote in message
news:dd******** *************** *********@4ax.c om...

Here's a blurb cut from A97 HELP on BOF/EOF:
When you open a Recordset object that contains at least one record,
the first record is the current record and the BOF and EOF properties
are False; they remain False until you move beyond the beginning or
end of the Recordset object by using the MovePrevious or MoveNext
method, respectively.

From that HELP blurb, it would seem that the .MoveFirst in the lines
below is simply not needed. Would you agree? Am I incorrect?

Set rstRRs = .OpenRecordset( dbOpenSnapshot)
With rstRRs
If .BOF = True Then GoTo NoRecs
.MoveFirst
Do Until rstRRs.EOF
If Int(Now()) - !DateSigned < WaitTime Then GottaWait = True
...

I would like to take the .MoveFirst out if it is not needed.