Re: Struggling with current record
From: Van T. Dinh (VanThien.Dinh_at_discussions.microsoft.com)
Date: 08/28/04
- Next message: Laurel: "current record vs record count"
- Previous message: Laurel: "Re: Struggling with current record"
- In reply to: Laurel: "Re: Struggling with current record"
- Next in thread: Cheval: "Struggling with current record"
- Messages sorted by: [ date ] [ thread ]
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.
-- HTH Van T. Dinh MVP (Access) "Laurel" <FakeMail@Hotmail.com> wrote in message news:eHthcjJjEHA.1348@tk2msftngp13.phx.gbl... > > 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 the > RecordCount value to be valid. If one tests RecordCount before executing > the MoveLast, MoveFirst, what is the point of those statements? >
- Next message: Laurel: "current record vs record count"
- Previous message: Laurel: "Re: Struggling with current record"
- In reply to: Laurel: "Re: Struggling with current record"
- Next in thread: Cheval: "Struggling with current record"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|