Re: Sorting / Grouping and sorting in the stored procedure
- From: "Douglas J. Steele" <NOSPAM_djsteele@xxxxxxxxxxxxxxxxx>
- Date: Wed, 5 Mar 2008 17:31:41 -0500
"Gabriele Bertolucci" <"info[at]pbsoft[dot]it"> wrote in message
news:ydme52qmue6f$.svkukoj8wudo$.dlg@xxxxxxxxxxxxx
I have a fairly dynamic selection screen for user input for report
criteria
including sort fields and Top n (records or percent or Ntile).
Up to this point I have allowed Access to sort the returned record set
based
upon Sorting and Grouping criteria. To my knowledge you can¢t turn this
off
short of deleting the grouping. With the addition of Top / Rank criteria
the
sp MUST sort / rank to return the proper records.
My questions is if the retuned record set is presorted, does this help,
hurt
or have no effect upon the access report?
When you use "Sorting and Grouping" feature, Access ALWAYS group/sort
AGAIN
the recordset that is returned, independently from what is the data
source.
Seo, if you want to sort/group data in a report, I suggest you to avoid
sorting or grouping in a stored procedure and let Access do this job.
Not only that, but you cannot be sure that Access will respect the order of
the incoming data.
I agree with Garbriele that you should let Access do the sorting for you.
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
.
- Follow-Ups:
- References:
- Re: Sorting / Grouping and sorting in the stored procedure
- From: Gabriele Bertolucci
- Re: Sorting / Grouping and sorting in the stored procedure
- Prev by Date: Re: Sorting / Grouping and sorting in the stored procedure
- Next by Date: Re: Sorting / Grouping and sorting in the stored procedure
- Previous by thread: Re: Sorting / Grouping and sorting in the stored procedure
- Next by thread: Re: Sorting / Grouping and sorting in the stored procedure
- Index(es):
Relevant Pages
|