Thanks for the thoughtful response, Steve.
I try to explain the problem more clearly, maybe you know a better way how
to handle it:
I'm working on a project with a group of volunteers. We have no fixed
working hours, most of the work is done in the evening and on weekends.
For the duration of a task I can only make rough assumptions (Design a
poster: about 1 wk, no matter how many hours). I know when certain tasks
must be finished, and the order in which certain tasks must be done. I can
then use the assumed duration to find out when we should start working on
something.
One problem I have with the standard calendar is, that a task that starts
on Friday and takes 2 days ends on Monday according to MSProject, not on
Saturday, like it should. Assigning the 24h calendar fixes the problem.
Not elegant, I agree.
Another annoyance for me is this: While setting up the plan, I decide a
task will take 2 days instead of one, the resource is set to 50%. Very
smart, but it has never happened in all the years I've been using this
program (not my main occupation) that I wanted this. Is there an option I
overlooked? A way of asking MSProject not to be smart until I'm actually
asking for help?
Thanks a lot!
Cheers,
Ralf.