I posted the other day about creating school pages and all of you were
extremely helpful. Thank you! I have another issue today.
I'm trying to create a department directory where we list the six main
divisions and then indented a little bit are the departments that fall under
that division
http://tutorial150.easycfm.com/ (text was still in my clipboard from
pasting it to another thread not more than 5 minutes ago) :)
On 7/21/06, Steven Sprouse [EMAIL PROTECTED] wrote:
I posted the other day about creating school pages and all of you were
extremely helpful. Thank you! I have
E-mail: [EMAIL PROTECTED]
-Original Message-
From: Steven Sprouse [mailto:[EMAIL PROTECTED]
Sent: Friday, July 21, 2006 9:58 AM
To: CF-Talk
Subject: Creating an indented department directory
I posted the other day about creating school pages and all of you were
extremely
I think I can digest this and make it happen. Thanks so much!!
~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four
times a
Charlie,
so in my case, the Division would be the genre, the Department would be the
author, and the sub-department would be the book name, correct?
In designing my table then, where the genre was entered in the book table,
would I have to write out each division name or should I replace
if there's a one-to-many relationship between Divisions and
Departments (one Division has many Departments), it's generally
considered good form to have two tables...one for Division and one for
Department), where DivisionID is a primary key in the Division table,
and a foreign key in the
Okay, so I understand the Division and Departments ID thing. Now, what if
there is a sub-department of a department? For example: We have a division of
Instruction...under that division we have a department of Curriculum
Instruction. Under the CI department we have sub-departments like
sub-departments might bet their own table. depends. are
sub-departments also departments in and of themselves (e.g. would a
sub-department be directly under a division? or only under another
department)? if it's the latter, then i would suggest a
sub-department table. If it's the former, then
Could I do this...
In my Departments table create a field that is called SubDept and have it be
either yes or no and another field called SubDeptID and allow null values so if
a dept isn't a sub-department of something it stays blank, but if it is it will
have a number that corresponds to the
depends...are sub-departments actually departments in and of
themselves? would a department ever be beneath a division as well as
beneath another department?
if they are truly sub-departments, then i'd break them out into a
sub-department table. no need to get overly complex.
On 7/21/06,
10 matches
Mail list logo
