That would not be incorrect. What defines "correct" is the scheduling
policies in place for your program. So, you can place a deadling on a
summary task. The subordinate discrete tasks may have their own deadlines
but thatm might pollute a good view of the critical path.
Personally, I would have a milestone: Deliver to Customer and put a
deadliine on that rather than a summary.
--
If this post was helpful, please consider rating it.
Jim
Visit
http://project.mvps.org/ for FAQs and more information
about Microsoft Project