New developement 3 tier structure

  • Thread starter Thread starter csgraham74
  • Start date Start date
C

csgraham74

Hi Guys,

I was hoping someone could point me in the right direction regarding a
new software developement.

Basicallly i have a friend who wants me to develop a dynamic system in
ASP.Net that allows me to create INSTITUTIONS at the top level then
each Institution can have multiple SUBGROUPS. Finally each subgroup can
have multiple SUBSUBGROUPS if you know what i mean. so basically this
is a three tier structure. Does anyone have any ideas on the best way
to code this from the point of view of giving the user a friendly
administration faciltiy ???

I think this will be complex but if anyone has any ideas or tips they
can share please let me know as i dont know the best way to go about
this.

all help appreciated

CG
 
Treeviews are pretty much always an easy to read control. Depending on what
you exactly need and what is the knowledge of the user that will use the
"administration facility", you could do a complex or not so complex page
based on a treeview display of your organisation displaying only the
institutions, subgroups and subsubgroups the user has the right to view
(depending if there are user rights involved)...

Institution
Sub Group1
Sub Sub Group1
Sub Sub Group2
Sub Sub Group3
Sub Group2
Sub Sub Group1
Sub Sub Group2
Sub Sub Group3
....

I hope it helps
 
thanks for that - but i dont think ive got access to treeview in
ASP.Net. If i do could you point me in the right direction.

I get the feeling this will get quite complex with multiple tables and
groups - any ideas on how to set up database structure ????


Thanks

CG
 
if you are using framework 2.0 I think there is a Treeview server control...
if using 1.0 or 1.1, you're right, you don't have one, but many are
available on the net...

for database, you simply reference the parent from the child row... for
example, each SubGroup record (row) has a reference to an Institution
record...

I hope it helps

ThunderMusic
 
In the database itself, you don't need to have much of a distinction between
the institution, the group, the subgroup, the sub-sub-group etc. They all
go in a single table.

table containerobject
containerid int identity
containerparent int
containername varchar(20)
end table

using this type of structure, each row simply has a primary key (the
containerid) and a reference to a parent row. The institutions themselves
have a parentid of 0. Index the containerparent column. Then, for each
item, you can easily find its children by looking for all the rows where the
containerparent is equal to the rows containerid.

Drilldown becomes an act of starting at the top, selecting an item and
watching the page display the children. You can do this quite nicely with
Ajax controls (see http://atlas.asp.net ).

--- Nick


--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
 
Back
Top