I have been requested to design a database (MSSQL 2000), that will "track" projects. There will be "Major" projects, which could have any amount of sub-projects, and these sub-projects could have any amount of sub-sub-projects.
All the projects/sub-projects/sub-sub-projects will have the exact same fields. It wont be overly complicated in regards to fields, i.e date started, status, deadlines, objectives. To me it looks like a single table could do the trick, as all projects/sub-projects/sub-sub-projects will have the same fields.
I'm just trying to get my head around how it all will work, how would you differentiate what was a sub-project or a sub-sub-project's parent?