A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Setting Up & Running Reports
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

order by property



 
 
Thread Tools Display Modes
  #1  
Old May 19th, 2004, 07:41 PM
JOHN HUSTON
external usenet poster
 
Posts: n/a
Default order by property

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.
  #2  
Old May 19th, 2004, 10:27 PM
Marshall Barton
external usenet poster
 
Posts: n/a
Default order by property

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.

--
Marsh
MVP [MS Access]
  #3  
Old May 19th, 2004, 10:54 PM
external usenet poster
 
Posts: n/a
Default order by property

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.



-----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.

--
Marsh
MVP [MS Access]
.

  #4  
Old May 20th, 2004, 01:08 AM
Marshall Barton
external usenet poster
 
Posts: n/a
Default order by property

wrote:

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.
--
Marsh
MVP [MS Access]



-----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.


  #5  
Old May 20th, 2004, 04:24 PM
external usenet poster
 
Posts: n/a
Default order by property

Still didnt help, but if I take out any level of previous
grouping it does
-----Original Message-----
wrote:

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.
--
Marsh
MVP [MS Access]



-----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.


.

  #6  
Old May 20th, 2004, 06:18 PM
external usenet poster
 
Posts: n/a
Default order by property

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

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.
--
Marsh
MVP [MS Access]



-----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.


.

  #7  
Old May 21st, 2004, 12:09 AM
Marshall Barton
external usenet poster
 
Posts: n/a
Default order by property

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]




wrote:

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

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.

  #8  
Old May 21st, 2004, 12:43 AM
external usenet poster
 
Posts: n/a
Default order by property

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]




wrote:

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

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.

.

  #9  
Old May 21st, 2004, 04:50 AM
Marshall Barton
external usenet poster
 
Posts: n/a
Default order by property

wrote:

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.



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]




wrote:

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

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.

.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 02:55 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.