Actually, whether or not RecordCount will be reliable depends on the
context.
If it's a DAO recordset and you're opening a table directly, it will be
accurate even if you haven't traversed the recordset. I believe there are
one or two other instances when it's accurate without having to do a
MoveLast (maybe in ordered recordsets where it has to run the whole thing
anyway?), but as Doug says, you're generally best assuming you should move
to the last record before relying on RecordCount as accurate.
If it's an ADO recordset, I don't believe it's ever accurate when first
opened until you've hit the last record (unless, of course, it's a 0- or
1-record set).
In any of the above instances, though, RecordCount should be 1 or more if
there is at least one record in the set, and should be 0 only if there are
none.
Rob