Rocky Smolin
rockysmolin at bchacc.com
Wed Aug 8 18:51:47 CDT 2012
I always do this on an app which is processing a recordset sequentially. I display the total number of records in a text box. And then have another text box which displays a counter. That box is updated every 100 records (otherwise the numbers just whiz by and you can't read them). I bump the counter every time through the loop and use modulo 100 division to know when to update the current record counter. It gives the user a sense of how long it will take to complete the processing - as opposed to there appearing to be nothing going on. SO the user knows the machine's not just hung - but is processing the records. Rocky -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins Sent: Wednesday, August 08, 2012 4:35 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] MoveFirst needed in DAO? In many instances I have need to know how many records are found, to do that you need to movelast then movefirst. Especially if you are then going to loop thru those records. Of course, often you don't care how many are found and a >0 count will do. If I am going to loop I will always put in a MoveFirst to be sure it is at the top. Maybe redundant? -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters Sent: Thursday, 9 August 2012 12:41 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] MoveFirst needed in DAO? I've always seen that in a newly opened DAO recordset, the recordset is always positioned at the first record - IF THERE ARE ANY RECORDS! So for most recordsets a check to see if any records exist is needed. Dan -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust Sent: Wednesday, August 08, 2012 9:17 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] MoveFirst needed in DAO? In DAO, the newly opened recordset is positioned at BOF but not necessarily on a record, IIRC. Charlotte On Wed, Aug 8, 2012 at 2:09 AM, Gustav Brock <gustav at cactus.dk> wrote: > Hi all > > Having opened a DAO recordset: > > Set rst = dbs.OpenRecordset(strSQL) > > often the first code line following is: > > rst.MoveFirst > > or, if the recordset can be empty: > > If rst.RecordCount > 0 Then > rst.MoveFirst > EndIf > > But is that really necessary? At which record could the recordset > possibly be positioned if not at the first? > > Even a snapshot or an ODBC linked recordset will not - as far as I > know - move anywhere until you tell it to do so. > > For ADO recordsets it is different as the recordcount can be -1 until > you, for example, have done a MoveLast. > > /gustav > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com