Ben --
It depends what your definition of "bad" is. Some do not recommend the use
of dependencies between summary tasks because it can result in circular
reference errors, especially when used in a master project. Others do not
recommend it because summary tasks are not "tasks" in the truest sense of
the word, and feel that dependencies should only be created between real
tasks. I am comfortable with these arguments, but on the other hand, I have
set dependencies between summary tasks for a number of years with no
negative results. Perhaps the others will have differing opinions. Hope
this helps.
