Queries with sorting vs. Orderby

[Thomas Kroljic]

All,

Do I gain any speed by assigning a query that is already created with the
proper sort order to the record source of a form vs. using the orderby on a
form (recordset)? I'm wondering if I should create multiple queries with the
sort orders I need vs. using the orderby property on the form.

I'm trying to increase the time it takes to open up a list of records based
on a users choice of sorting.

Thank You,
Thomas j. Kroljic

 

[peregenem]

Do I gain any speed by assigning a query that is already created with the
proper sort order to the record source of a form vs. using the orderby on a
form (recordset)? I'm wondering if I should create multiple queries with the
sort orders I need vs. using the orderby property on the form.

From a 'logical' point of view, unless they are 'data driven' custom

sort orders are best done in the front end IMO. Multiple stored Query
objects (VIEWs) with the same SQL code bar the ORDER BY clauses sounds
like a potential maintenance problem.

From a 'physical' point of view, when you consider that ORDER BY is

done by cursor (and I mean data cursor, not that blinking character on
the screen) and a recordset essentially *is* a cursor, there isn't
going to be much to choose between server side and client side so you
would need to do some testing based on circumstances e.g. DAO or ADO,
Jet or ADP, etc.