Advice on database design

[Shannon]

Hi,

How would i design my database to work like this:

We have 5 functional teams in the database.
Four of those team can only have access to their own
teams.
Fifth team will have access for everything but can only
edit specific area on the form record such as budget.

Now this database will have the WBS # (work breakdown
structure) to be unique ID the WBS # can be something like
this 5.4.1.2.3. Each level is identified by a period.
Level 1 is 5.4
level 2 is 5.4.1
level 3 is 5.4.1.2 and so on

User should be able to add/edit record at any level.
For example, add/edit record at level 5.4 is 5.5, 5.6, and
so on or go to the next level 5.4.1.1, 5.4.1.2, and so on.

Please help me design this out, thanks,

 

[John Vinson]

Hi,

How would i design my database to work like this:

We have 5 functional teams in the database.
Four of those team can only have access to their own
teams.
Fifth team will have access for everything but can only
edit specific area on the form record such as budget.

Now this database will have the WBS # (work breakdown
structure) to be unique ID the WBS # can be something like
this 5.4.1.2.3. Each level is identified by a period.
Level 1 is 5.4
level 2 is 5.4.1
level 3 is 5.4.1.2 and so on

User should be able to add/edit record at any level.
For example, add/edit record at level 5.4 is 5.5, 5.6, and
so on or go to the next level 5.4.1.1, 5.4.1.2, and so on.

Please help me design this out, thanks,

This kind of structure is a MAJOR pain to handle relationally. At the
very least, you should have five (or more? how many levels are
allowed?) fields rather than using a text string - 5.10 will sort
BEFORE 5.9.8.3.5 (since the text string "1" sorts before the text
string "9".