order by property

  • Thread starter Thread starter JOHN HUSTON
  • Start date Start date
J

JOHN HUSTON

I am trying to sort a report by date using the "order by"
property. If I have only two levels of grouping it
workes fine, but if I add a third level then it will no
longer sort. Has anyone run into this problem before?
Thank you for your help.
 
JOHN said:
I am trying to sort a report by date using the "order by"
property. If I have only two levels of grouping it
workes fine, but if I add a third level then it will no
longer sort. Has anyone run into this problem before?
Click to expand...


The report's Sorting and Grouping will take precendence over
whatever is in the report's OrderBy property. You should
specify the sorting in Sortng and Grouping's lowest level.

I don't understand what you mean by a 3rd level no longer
sorting and will need more information before addressing
whatever the issue is.
 
What I mean is: Originally I had grouping levels of:
1. Department
and
2. Model
the rpts "Order by" was entry date, and it worked fine.
Well, all I did was add a top grouping level of
1. Dealership
and thats all I changed and now it wont sort by any field
much less the date.
 
What I mean is: Originally I had grouping levels of:
1. Department
and
2. Model
the rpts "Order by" was entry date, and it worked fine.
Well, all I did was add a top grouping level of
1. Dealership
and thats all I changed and now it wont sort by any field
much less the date.
Click to expand...


Let's try setting Sorting and Grouping to:

Dealership
Department
Model
EntryDate

and see what results you get.
--
Marsh
MVP [MS Access]


 
Still didnt help, but if I take out any level of previous
grouping it does
-----Original Message-----
What I mean is: Originally I had grouping levels of:
1. Department
and
2. Model
the rpts "Order by" was entry date, and it worked fine.
Well, all I did was add a top grouping level of
1. Dealership
and thats all I changed and now it wont sort by any field
much less the date.
Click to expand...


Let's try setting Sorting and Grouping to:

Dealership
Department
Model
EntryDate

and see what results you get.
--
Marsh
MVP [MS Access]


precendence
over
Click to expand...

.
Click to expand...
 
No that didnt work either
-----Original Message-----
What I mean is: Originally I had grouping levels of:
1. Department
and
2. Model
the rpts "Order by" was entry date, and it worked fine.
Well, all I did was add a top grouping level of
1. Dealership
and thats all I changed and now it wont sort by any field
much less the date.
Click to expand...


Let's try setting Sorting and Grouping to:

Dealership
Department
Model
EntryDate

and see what results you get.
--
Marsh
MVP [MS Access]


precendence
over
Click to expand...

.
Click to expand...
 
Come on man, give me a clue about what happened. "didn't
work" is just not enough to go on, especially with a
situation that appears to me to be rather ordinary. Try
posting a sample of what the report looks like and explain
what you want it to be.
 
Ok, I start with two grouping levels. Dealer and
underneath that Department. The query I am baseing the
report on has been whittled down to only three fields:
Dealer Dept. and Date. If I set the reports "Orderby" to
Date just like this it works fine.
But
If I simply add the field "Model" the the query, and then
make Model the 3rd level of grouping in the report. The
records will no longer be sorted by date.
I have tried changing the order of the fields in the query
(putting date everywhere from first to last and setting
its sorting property), and adding an Date grouping level
at the end which didnt work either.
If I start with the report that doesnt sort properly, and
all I do is remove ANY level of grouping It works. I
have tried every simple thing that I can think of. This
is a report that has worked fine for years but recently
it has had the need for the extra top level of grouping
(dealership).
I have also tried to build this report over with the
report wizard, adding only the 4 needed fields, and
setting date to sort, and that didnt work either. Thank
you for your help Marshall.

-----Original Message-----
Come on man, give me a clue about what happened. "didn't
work" is just not enough to go on, especially with a
situation that appears to me to be rather ordinary. Try
posting a sample of what the report looks like and explain
what you want it to be.
--
Marsh
MVP [MS Access]




No that didnt work either will
no
Click to expand...
.
Click to expand...
 
Ok, I start with two grouping levels. Dealer and
underneath that Department. The query I am baseing the
report on has been whittled down to only three fields:
Dealer Dept. and Date. If I set the reports "Orderby" to
Date just like this it works fine.
But
If I simply add the field "Model" the the query, and then
make Model the 3rd level of grouping in the report. The
records will no longer be sorted by date.
I have tried changing the order of the fields in the query
(putting date everywhere from first to last and setting
its sorting property), and adding an Date grouping level
at the end which didnt work either.
If I start with the report that doesnt sort properly, and
all I do is remove ANY level of grouping It works. I
have tried every simple thing that I can think of. This
is a report that has worked fine for years but recently
it has had the need for the extra top level of grouping
(dealership).
I have also tried to build this report over with the
report wizard, adding only the 4 needed fields, and
setting date to sort, and that didnt work either. Thank
you for your help Marshall.
Click to expand...


I can't imagine how adding a top group level would affect
the sorting in the third group level, other than the date
being split into different groups.

It is well known that sorting in the query will have no
effect when the report has anything in its Sorting and
Grouping, but the report's OrderBy property should be
applied after the sorting and grouping has ordered the
records.

Other than some kind or corruption, the only thing I can
think of is that the date is somehow being converted to a
string and the sorting is being done on the string instead
of a date value.

Straw grasping now, but your date field is not reallt named
Date is it?? If it is, then Access may be interpreting it
to be the Date function, which will of course make it appear
that the soring didn't do anything.

Sorry, but I just don't have any other ideas about this
mysterious issue.
--
Marsh
MVP [MS Access]

-----Original Message-----
Come on man, give me a clue about what happened. "didn't
work" is just not enough to go on, especially with a
situation that appears to me to be rather ordinary. Try
posting a sample of what the report looks like and explain
what you want it to be.
--
Marsh
MVP [MS Access]




No that didnt work either
-----Original Message-----

What I mean is: Originally I had grouping levels of:
1. Department
and
2. Model
the rpts "Order by" was entry date, and it worked fine.
Well, all I did was add a top grouping level of
1. Dealership
and thats all I changed and now it wont sort by any
field
much less the date.


Let's try setting Sorting and Grouping to:

Dealership
Department
Model
EntryDate

and see what results you get.


-----Original Message-----
JOHN HUSTON wrote:

I am trying to sort a report by date using the "order
by"
property. If I have only two levels of grouping it
workes fine, but if I add a third level then it will
no
longer sort. Has anyone run into this problem before?


The report's Sorting and Grouping will take
precendence
over
whatever is in the report's OrderBy property. You
should
specify the sorting in Sortng and Grouping's lowest
level.

I don't understand what you mean by a 3rd level no
longer
sorting and will need more information before
addressing
whatever the issue is.
Click to expand...
.
Click to expand...
Click to expand...
 
Back
Top