Well all I can say is if you want chain tasks then you need to use predecessors. It really doesn't matter about the departments it's just a question of whether a particular task is allowed to start until any previous task or tasks identified as pPractical problem is that while this effort to specify which tasks are dependent on other tasks is worth the effort if you have some kind of standard list of tasks and he use the built-in function in QuickBase to replicate those set of tasks into a project then the effort is worth it.
But if you are just entering Task on the fly in my experience users will balk at the extra data entry to identify the predecessor task(s).
I just implemented a wonderful tool from MCF which allows for a completely different visual drag and drop interface where you drag and drop the tasks on a grant chart and drag and drop the task dependencies. My opinion that is the only practical way to get users to identify task predecessors if you have non-standard set of tasks for projects.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------