Normalizing Tree Data

#21

cr113 wrote:

Quote:

On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
Division
Manager
Employee

What are your most important queries using the tree?

#22

cr113 wrote:

Quote:

On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
Division
Manager
Employee

What are your most important queries using the tree?

#23

cr113 wrote:

Quote:

On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
Division
Manager
Employee

What are your most important queries using the tree?

#24

cr113 wrote:

Quote:

On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
Division
Manager
Employee

What are your most important queries using the tree?

#25

cr113 wrote:

Quote:

On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
Division
Manager
Employee

What are your most important queries using the tree?

#26

On Feb 8, 2:41*pm, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:

Quote:

cr113 wrote:
On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
* * Division
* * * * Manager
* * * * * * Employee

What are your most important queries using the tree?- Hide quoted text -

I'm not sure. It depends on how I set up my tables. I'll need to be
able to display the entire tree (using a TreeView object in Visual
Studio if you are familiar with that). Add/Edit nodes. Delete a node
and it's underlying children.

Have you looked at the way my tables are set up in my example? Am I at
least in the ballpark? Should I include a "level" field in the ID
table perhaps (root = level 0, children of root = level 1, etc)?

#27

On Feb 8, 2:41*pm, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:

Quote:

cr113 wrote:
On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
* * Division
* * * * Manager
* * * * * * Employee

What are your most important queries using the tree?- Hide quoted text -

I'm not sure. It depends on how I set up my tables. I'll need to be
able to display the entire tree (using a TreeView object in Visual
Studio if you are familiar with that). Add/Edit nodes. Delete a node
and it's underlying children.

Have you looked at the way my tables are set up in my example? Am I at
least in the ballpark? Should I include a "level" field in the ID
table perhaps (root = level 0, children of root = level 1, etc)?

#28

On Feb 8, 2:41*pm, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:

Quote:

cr113 wrote:
On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
* * Division
* * * * Manager
* * * * * * Employee

What are your most important queries using the tree?- Hide quoted text -

I'm not sure. It depends on how I set up my tables. I'll need to be
able to display the entire tree (using a TreeView object in Visual
Studio if you are familiar with that). Add/Edit nodes. Delete a node
and it's underlying children.

Have you looked at the way my tables are set up in my example? Am I at
least in the ballpark? Should I include a "level" field in the ID
table perhaps (root = level 0, children of root = level 1, etc)?

#29

On Feb 8, 2:41*pm, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:

Quote:

cr113 wrote:
On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
* * Division
* * * * Manager
* * * * * * Employee

What are your most important queries using the tree?- Hide quoted text -

I'm not sure. It depends on how I set up my tables. I'll need to be
able to display the entire tree (using a TreeView object in Visual
Studio if you are familiar with that). Add/Edit nodes. Delete a node
and it's underlying children.

Have you looked at the way my tables are set up in my example? Am I at
least in the ballpark? Should I include a "level" field in the ID
table perhaps (root = level 0, children of root = level 1, etc)?

#30

On Feb 8, 2:41*pm, Bob Badour <bbad... (AT) pei (DOT) sympatico.ca> wrote:

Quote:

cr113 wrote:
On Feb 8, 11:42 am, TroyK <cs_tr... (AT) juno (DOT) com> wrote:

On Feb 8, 10:10 am, cr113 <cr... (AT) hotmail (DOT) com> wrote:

What's the simplest way to set up a relationional database with tree
data? I'm more interested in simplicity vs speed.

snip - see OP

People will be able to guide you better if you can expand more on what
criteria are important to you.

Here are some specifics: I'm using Access. There will only be a few
thousand records maximum in any table. Around 4-6 fields in each
table. Very few concurrent users. The users need to be able to add/
edit/delete any of the nodes in the tree. There are 4 levels in the
tree. Expanding the previous example it would look something like
this:

Company
* * Division
* * * * Manager
* * * * * * Employee

What are your most important queries using the tree?- Hide quoted text -

I'm not sure. It depends on how I set up my tables. I'll need to be
able to display the entire tree (using a TreeView object in Visual
Studio if you are familiar with that). Add/Edit nodes. Delete a node
and it's underlying children.

Have you looked at the way my tables are set up in my example? Am I at
least in the ballpark? Should I include a "level" field in the ID
table perhaps (root = level 0, children of root = level 1, etc)?