FindFirst method is very slow

[EricB]

I have recently upsized some of my access tables to SQL
and noticed that the routines that are using the
FindFirst method are extremely slow, all my customers are
complaining. It used to be very fast when using linked
access tables. Can anyone please explain why this is
happening? TIA.
Eric.

 

[Rick Brandt]

I have recently upsized some of my access tables to SQL
and noticed that the routines that are using the
FindFirst method are extremely slow, all my customers are
complaining. It used to be very fast when using linked
access tables. Can anyone please explain why this is
happening? TIA.
Eric.

When moving to ODBC/server type databases you need to abandon the built in
"Find" tools. Instead you should apply filters to the form to return ONLY
the records that the user wants. This is much more efficient than "Find"
even with Access/Jet tables but you just get away with it more in that
environment.

 

[Tim Ferguson]

I have recently upsized some of my access tables to SQL
and noticed that the routines that are using the
FindFirst method are extremely slow, all my customers are
complaining. It used to be very fast when using linked
access tables. Can anyone please explain why this is
happening?

I would guess that it's due to moving large amounts of data across a
network: you'll probably find the NW admin after you soon too!

What about doing all the selection on the server instead? Get rid of all
the FindFirst criteria and put them into WHERE clauses instead. Don't
fetch data that you don't intend to use!

HTH


Tim F