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

Simple question (I hope!!) on .FindFirst

P: n/a
Hi all
Simple question re .findfirst
Is it true it does not use any indexes and really the best option with
a SQl backend (ignoring using Stored Procedures which at this stage
has not been funded) is to open recordsets with specific SQL to
retreive small recordsets (and EOF indicating .nomatch)
I found a conversion from Access to SQL caused soem of the .FindFirst
calls to become really slow, tabels are indexed correctly. Initial
tests show thta using recordsets where a select command is past seems
to make a nig differance
Cheers
Shaun
Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Look at the Seek method in the Help file. It is much faster than findfirst
but is limited in where it can be used.

--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdatasheet.com
www.pcdatasheet.com
"Shaun" <sh********@msn.com> wrote in message
news:4a*************************@posting.google.co m...
Hi all
Simple question re .findfirst
Is it true it does not use any indexes and really the best option with
a SQl backend (ignoring using Stored Procedures which at this stage
has not been funded) is to open recordsets with specific SQL to
retreive small recordsets (and EOF indicating .nomatch)
I found a conversion from Access to SQL caused soem of the .FindFirst
calls to become really slow, tabels are indexed correctly. Initial
tests show thta using recordsets where a select command is past seems
to make a nig differance
Cheers
Shaun

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.