Re: I WANT REPORTS IN ACCESS TO INDEX IN THE SAME MANNER I HAVE TH

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Larry Linson (bouncer_at_localhost.not)
Date: 01/31/05


Date: Sun, 30 Jan 2005 22:18:12 -0600

Is the Field you chose on which to sort actually a Field in the RecordSource
of the Report?

That message implies that it is due to an expression being evaluated. It
could result from something other than your adding the Sort, though it
certainly is suspicious that it happened just after you chose a Field on
which to Sort.

Just for the record, what version of Access are you using, and what is the
level of Service Pack that has been applied (both should be available from
Help | About)?

  Larry Linson
  Microsoft Access MVP

"ARNYS" <ARNYS@discussions.microsoft.com> wrote in message
news:2CFA3DBA-579C-463C-9DC7-C9B9C8544517@microsoft.com...
> This was good advice and I tried it and I got the following message:
>
> "This report is to complicated to complex to be evaluated. For example, a
> numeric expression may contain too many complicated elements. Try
> simplifying the expression by assigning parts of the expression to
variables."
>
> I went to sorting and grouping in the report design mode and chose a field
> to be indexed and selected ascending and got the message above when I
> previewed the report. The group properties are marked as follows:
>
> group header no
> group footer no
> group on blank
> group interval 1
> keep together no
>
> I cannot figure out how to make that message go away so the report will
run
> and be indexed as I desire it.
>
> thanks for the help!
>
> Arny
>
> "Larry Linson" wrote:
>
> > "ARNYS" <ARNYS@discussions.microsoft.com> wrote
> >
> > For other good suggestions on effective use of newsgroups, see the FAQ
at
> > http://www.mvps.org/access/netiquette.htm.
> >
> > In addition to putting the question in the body of the post, you'll find
> > that posting in all caps is considered "shouting" and considered to be
> > impolite.
> >
> > Guessing your issue was "I want the data in my reports sorted in the
same
> > order as the query I am using for record source," I will have to tell
you,
> > "Sorry, the order of the RecordSource of a Report or Form is not
material.
> > You must specify the sort order in the Report's Sorting and Grouping
> > Properties."
> >
> > Larry Linson
> > Microsoft Access MVP
> >
> >
> >
> >



Relevant Pages

  • Re: subreport in detail line..sortable?
    ... In order to sort the main report by a field in the subreport, you must get that field into the RecordSource of the main report. ...
    (microsoft.public.access.reports)
  • Re: Report in FM 6 or 7
    ... Please adivse on this- and then, I get to attack this report again in ... you cannot sort by AgeDivision_Category and why the Export/Import ... act they want to be the last act of the show, they have to sort by their ... If the Age Division field contains data in the form "3-5 Age Division" ...
    (comp.databases.filemaker)
  • Re: Report in FM 6 or 7
    ... Please adivse on this- and then, I get to attack this report again in ... you cannot sort by AgeDivision_Category and why the Export/Import ... act they want to be the last act of the show, they have to sort by their ... If the Age Division field contains data in the form "3-5 Age Division" ...
    (comp.databases.filemaker)
  • Re: sort in report
    ... "fredg" wrote: ... date on my report. ... fields I would like to sort on in a report: ... so the format is irrelevant). ...
    (microsoft.public.access.gettingstarted)
  • Re: Report in FM 6 or 7
    ... Please adivse on this- and then, I get to attack this report again in ... you cannot sort by AgeDivision_Category and why the Export/Import ... act they want to be the last act of the show, they have to sort by their ... If the Age Division field contains data in the form "3-5 Age Division" ...
    (comp.databases.filemaker)