I would suggest that every so often the project Server box needs to restart
and if he has the project checked out, all changes made after that date will
get lost, so if he doesn't want to lose work he should check the project in
each time. If his PC is on the end of a very slow network, then I could
understand why he might want it open, otherwise the behavior is a bit anal!
--
Rod Gill
Microsoft MVP for Project
Author of the only book on Project VBA, see:
http://www.projectvbabook.com
Andy, why does he insist on keeping it open? He must have a reason for it.
I
would want to find out why first.
Thanks
Marc
No reason whatsoever other than perceived convenience, stubbornness,
and because I suggested just the opposite. In other words, no
business reason at all. To top it off, this particular project is
one of those "support" projects where we're just creating tasks with
categories to book time resources are assigned ahead of time with 0
duration / 0 effort - not a "real" project. Once those are setup,
there shouldn't be any reason to get back in unless new employees come
on board.
We have a job that runs each night that automatically republishes all
project plans in the database (that C+ routine y'all have all seen out
there in a blog from a gentleman at Microsoft - which works well).
Seems to me that this would be reason enough to close it at the end of
the day so that the changes (if any) would be reflected in the draft
database and PWA would then be accurate.
