Depending on the type of recordset, you can use MoveLast to go to the end of
the recordset, at which point its RecordCount property will be correct. Once
you've done that, use MoveFirst to go back to the beginning, and do your
processing.
And while a picky point, the example you gave doesn't open the recordset
twice. They're two different recordsets.
--
Doug Steele, Microsoft Access MVP
<a style='text-decoration: underline;' href="http://I.Am/DougSteele" target="_blank">http://I.Am/DougSteele</a>
(No private e-mails, please)
"Darwin Weyh" <shtdev.delete.this.TakeThisOut@weyh.net> wrote in message
news:uD545kwGEHA.1968@TK2MSFTNGP12.phx.gbl...
> So if I understand all this right to get the proper record count I need to
> open the recordset twice:
> Once with the "select count(*) as reccount where ...."
> save the record count and then again with "select * where ...."
> to use the records.
>
> Or is there a better way?
>
> Darwin C. Weyh
> shtdev.delete.this.TakeThisOut@weyh.net
> And for the spammers: dweyh.TakeThisOut@weyh.net
>
> "Kevin Yu [MSFT]" <v-kevy.TakeThisOut@online.microsoft.com> wrote in message
> news:Dl8Qc%23EGEHA.2224@cpmsftngxa06.phx.gbl...
> > Hi Paul,
> >
> > It was nice to hear that you have had the problem resolved. Thanks for
> > sharing your experience with all the people here. If you have any
> > questions, please feel free to post them in the community.
> >
> > Kevin Yu
> > =======
> > "This posting is provided "AS IS" with no warranties, and confers no
> > rights."
> >
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: RecordCount method returning -1 for a recordset