Access, as you all probably know by now, does not allow a FindFirst method to be used with a table type object. You have to use the DFirst() function instead. But as your database grows larger, you will find that Danything() takes a darned sight longer than you are comfortable with.
It is easy to make a monkey of Access. And you can actually do a FindFirst on a Table by...
...something as simple as opening a recordset with SQL "Select * from [YourTable] order by [YourColumn];" and ...
...then using the FindFirst method on the recordset.
The advantages of doing something like this is that you have full control of what is happening. You also have faster access to the records as they have been stored in a recordset (in some memory area somewhere). When you use a DAnything(), Access looks through the table physically and disk access is always slower than memory access.
Not just that, once you have positioned yourself at the first record, you can carry on going through the records without having to do another query on the table.
This is not enough? Need to know more?
...See Also DLookup() versus FindFirst on a Recordset
| Back to MS Access Tips | Perfect Paradigm - A Solutions Company |