Why? As in "why do you care how many rows the table has?" With proper
indexing and data/table design, there should be few performance issues.
If you open a new query, select the table, add the fields you are interested
in, and add the field you are using to determine row number (NOTE: Access
doesn't "number" rows ... you have to add a field that imposes some sort of
sort order).
Now change the properties of the query -- right click in the open gray space
and select the TOP 100000 rows. Again, note that this will be based on
whatever you've told Access to sort by. If you haven't, there's no
guarantee you'll get the same 100000 rows the second time you run the query.
Regards
Jeff Boyce
Microsoft Office/Access MVP