Re: TOTAL COST COLUMN (IN TASK USAGE VIEW)
From: Adele Snoek (Snoek_at_discussions.microsoft.com)
Date: Wed, 13 Oct 2004 23:19:09 -0700
Thanks for the piece of code for the macro. I played around with it but
because I am not a VB programmer I no idea how to change and enhance your
code, so I got one of our developers to help me.
He has managed to get all the columns and calculations in the task usage
view that I want to see. Now my next question is:
In the task usage view the total cost column (MS Project default column)
adds up the cost of all the resources assigned to that task and puts it in
the task row. Then for all the roll ups it adds the totals for the different
levels, so if I were to roll up all the tasks and just have the main project
level displaying it shows the grand total. Now the customised columns that I
have put in - how do we write code to add the roll ups on the different
levels. My developer has managed to add up the resources attached to the
task, but from there on he doesn't know how to add the rest. Could you get
back to me on this one, I would really appreciate it as I am so close to
answering all my questions using MS Project instead of taking it to Excel and
doing the calculations there.
Thanks once again for your help.
082 330 1882
> You mention the Task Usage view but you don't talk about whether you
> want the new fields to be timescaled. If you don't care about the
> timescale values my previous suggestions of implementing a relatively
> simple macro to transfer the custom field values from a Resource view
> (i.e. Resource Sheet) to a Task view (i.e. Task Usage). I don't recall
> if formulas can be transferred (I suspect not) but all you really need
> transferred is the custom rate values. The formulas can either be
> replicated in the custom Task fields once the data is transferred or,
> they can easily and more efficiently be included in the VBA code.
> If you are interested in timescale values then you have no choice but to
> write a custom VBA macro to export the data to Excel. Custom fields are
> static, that is, Project cannot timescale them since it has no way of
> determining how to make the allocation over time. But, an algorithm can
> be developed to effectively timescale custom field values in any way
> necessary. I have done it several times.
> Hope this helps.
> Project MVP