Re: Struggling with current record
Date: Sat, 28 Aug 2004 11:15:14 +1000
The RecordCount before the MoveLast only counts the Records / Rows that have
been populated at that time which may not be the true count. Hence, you
need the MoveLast for the true count.
However, for a *non-empty* Recordset, the RecordCount is never zero and an
empty Recordset always has zero RecordCount. Thus, I used the RecordCount =
0 whether the Recordset is empty or not.
Van T. Dinh
"Laurel" <FakeMail@Hotmail.com> wrote in message
> Getting there.
> The suggestion to use DoCmd.RunCommand acCmdSaveRecord to force the effect
> of having the user click on the new empty record seems to have solved most
> of my practical problems. Hopefully this is a theoretical question: My
> understanding was that the statements MoveLast, MoveFirst were to firce
> RecordCount value to be valid. If one tests RecordCount before executing
> the MoveLast, MoveFirst, what is the point of those statements?
- Re: how can i get the count of table records in ASP?
... >I used the movelast and movefirst and recordcount but it generates an ... > Rowset does not support fetching backward. ...
- Re: ... after Opening a record set
... > Hi this is one question that has been nagging me ... ... > the exact details anymore since I always forget to ask when it arises, ... Do I have to do a MoveLast ... The RecordCount is not always accurate of supported, depending on Provider and/or Cursor Location. ...
- Re: ADO episode
... I've seen reference about using MoveLast with ADO in order to set the ... sylvain aei ca (fill the blanks, no spam please) ... I think you are thinking of a DAO trick: with ADO, ... will not change the RecordCount property value. ...
- Re: Unbekannter Funktionsname
... > Auch die Prüfung auf RecordCount ist fehlerhaft, ... Hallo Michael, ... wenn die Abfrage Datensätze liefert. ... von Datensätzen vorher ein MoveLast machen muss. ...
- Re: How can I format label name as I loop through records?
... > of .RecordCount just before executing the 'Next' statement. ... >> Try putting a .MoveLast before your .MoveFirst statement. ... >> Doug Steele, Microsoft Access MVP ... >> (no e-mails, please!) ...