By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,880 Members | 2,292 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,880 IT Pros & Developers. It's quick & easy.

Changing, "FindFirst" to using the, "Seek" Method?

P: n/a

I ran a MS Access Analyzer program that suggested changing,
"rst.FindFirst strcriteria" to using the, "Seek" instead. I
tried making the change. I get a Compile error that says, "Argument
is not optional". Does anyone have any ideas on how I should change
the FindFirst to using Seek the method?

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Seek" is limited to use on Tables in the opened Database. It cannot be used
on Linked Tables. And, in many, many cases, using a Query with Criteria to
limit the Records returned to just those that are needed is preferrable to
using either .Seek or .Find. Chances are high that would boost performance
even more.

..Seek and .Find are used to locate to a specific record, but not to navigate
sequentially through a recordset.

The .Find and .Move methods work with either local or Linked Tables, and
make it easy to navigate sequentially through a recordset.

Using criteria in a Query should be the first thing you investigate.

Larry Linson
Microsoft Access MVP

"jphelan" <jp*********@earthlink.net> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...

I ran a MS Access Analyzer program that suggested changing,
"rst.FindFirst strcriteria" to using the, "Seek" instead. I
tried making the change. I get a Compile error that says, "Argument
is not optional". Does anyone have any ideas on how I should change
the FindFirst to using Seek the method?

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.