Publishing after accepting updates

J

JosieMarley

In Project 2003 when we accepted task updates it automatically opened the
respective schedules and then you could publish afterwards (usually
automatically on save).

Now in project 2007 it just adds it all into a queue. However the updates,
new tasks etc. don't get published on the acceptance because the updates are
all done off line.

I get dozens of task updates a day and have 42 current projects. I don't
want to have to open all 42 every day to republish just in case there has
been an update. So is there any 'best practice' out there to make sure
updates are published?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top