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  

general report question on hierarchy



 
 
Thread Tools Display Modes
  #1  
Old August 13th, 2009, 01:04 AM posted to microsoft.public.access.reports
JohnE
external usenet poster
 
Posts: 75
Default general report question on hierarchy

I have an application that works on a hierarchy (treeview) method. There is
a table that all the info is in. A field in the table is called IsChildOf
and another that indicates IsTopLevel. There can be multiple levels under
the top level or no levels under the top level.

I can see it coming that the users will want to see a hierarchy style report
from the app. So, I am wondering if anyone out there has ever done such a
report? If so, how? I have no idea where or how to begin something like
that. Any thoughts, suggestions, idea, and/or recommendations are
appreciated.

Thanks.

John
  #2  
Old August 13th, 2009, 07:03 AM posted to microsoft.public.access.reports
Allen Browne
external usenet poster
 
Posts: 11,706
Default general report question on hierarchy

This is not easy in JET, John.

How many generations do you need to go back? If 3 is enough, you may be able
to do it like this:
http://allenbrowne.com/ser-06.html

Beyond that, it starts to get more involved. One of the problems is the
possibility of entering a record as its own grandparent (or further
removed), in which case you have an infinite loop that can never be fully
resolved.

I'm not sure I would have the IsTopLevel: a null IsChildOf would indicate
that (for practical purposes) this record would be treated as being top
level. Other than that, the self-join is a wonderfully flexible design, even
if it is frustrating when you are ask to fully resolve it back through all
generations.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"JohnE" wrote in message
...
I have an application that works on a hierarchy (treeview) method. There
is
a table that all the info is in. A field in the table is called IsChildOf
and another that indicates IsTopLevel. There can be multiple levels under
the top level or no levels under the top level.

I can see it coming that the users will want to see a hierarchy style
report
from the app. So, I am wondering if anyone out there has ever done such a
report? If so, how? I have no idea where or how to begin something like
that. Any thoughts, suggestions, idea, and/or recommendations are
appreciated.

Thanks.

John


  #3  
Old August 13th, 2009, 01:39 PM posted to microsoft.public.access.reports
JohnE
external usenet poster
 
Posts: 75
Default general report question on hierarchy

Mr Browne, thanks for the info. So far, several levels is all I've seen.
Hopefully they don't get to carried away on it. The IsTopLevel had to be put
in. All requests go into the table. They stay there until it is reviewed
and prioritized or removed. At first the empty IsChildOf was considered top
level but after having hundreds show up as top level, the other field was
added.

Again, thanks for the info.
....John




"Allen Browne" wrote:

This is not easy in JET, John.

How many generations do you need to go back? If 3 is enough, you may be able
to do it like this:
http://allenbrowne.com/ser-06.html

Beyond that, it starts to get more involved. One of the problems is the
possibility of entering a record as its own grandparent (or further
removed), in which case you have an infinite loop that can never be fully
resolved.

I'm not sure I would have the IsTopLevel: a null IsChildOf would indicate
that (for practical purposes) this record would be treated as being top
level. Other than that, the self-join is a wonderfully flexible design, even
if it is frustrating when you are ask to fully resolve it back through all
generations.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"JohnE" wrote in message
...
I have an application that works on a hierarchy (treeview) method. There
is
a table that all the info is in. A field in the table is called IsChildOf
and another that indicates IsTopLevel. There can be multiple levels under
the top level or no levels under the top level.

I can see it coming that the users will want to see a hierarchy style
report
from the app. So, I am wondering if anyone out there has ever done such a
report? If so, how? I have no idea where or how to begin something like
that. Any thoughts, suggestions, idea, and/or recommendations are
appreciated.

Thanks.

John



  #4  
Old August 13th, 2009, 03:04 PM posted to microsoft.public.access.reports
Allen Browne
external usenet poster
 
Posts: 11,706
Default general report question on hierarchy

Okay: I understand that you may need to assign a record as being a top level
one, as distinct from one where the parent is unknown but it's not top
level.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"JohnE" wrote in message
...
Mr Browne, thanks for the info. So far, several levels is all I've seen.
Hopefully they don't get to carried away on it. The IsTopLevel had to be
put
in. All requests go into the table. They stay there until it is reviewed
and prioritized or removed. At first the empty IsChildOf was considered
top
level but after having hundreds show up as top level, the other field was
added.

Again, thanks for the info.
...John




"Allen Browne" wrote:

This is not easy in JET, John.

How many generations do you need to go back? If 3 is enough, you may be
able
to do it like this:
http://allenbrowne.com/ser-06.html

Beyond that, it starts to get more involved. One of the problems is the
possibility of entering a record as its own grandparent (or further
removed), in which case you have an infinite loop that can never be fully
resolved.

I'm not sure I would have the IsTopLevel: a null IsChildOf would indicate
that (for practical purposes) this record would be treated as being top
level. Other than that, the self-join is a wonderfully flexible design,
even
if it is frustrating when you are ask to fully resolve it back through
all
generations.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.


"JohnE" wrote in message
...
I have an application that works on a hierarchy (treeview) method.
There
is
a table that all the info is in. A field in the table is called
IsChildOf
and another that indicates IsTopLevel. There can be multiple levels
under
the top level or no levels under the top level.

I can see it coming that the users will want to see a hierarchy style
report
from the app. So, I am wondering if anyone out there has ever done
such a
report? If so, how? I have no idea where or how to begin something
like
that. Any thoughts, suggestions, idea, and/or recommendations are
appreciated.

Thanks.

John



 




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 12:36 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.