A family of Microsoft relational database management systems designed for ease of use.
E10E,
First, the Update Project feature is intended to facilitate a convenient "peanut butter" spread of progress to a point in time. It is really only applicable to level of effort (LOE) type activities wherein progress is indeed measured by the passage of time. However is sounds like you are using it as a measure of expected completion to a point in time.
I'm still confused by your steps. If I understand you goal it appears you are going through a whole lot more steps than necessary.
- If your macro copied the data for the % Complete field into another customized field, (It would be nice to know which field that is), where did the data in the % Complete field come from? Is this the data supposedly entered by the PM? If so, why not enter it directly into the custom field?
2, After using the Update Project function, why copy the data from % Complete to yet another field?
Why wouldn't this simpler approach work?
a. Have you PM enter an "actual" % complete value into Text1 as a whole number (i.e. 40%=40)
b. Run the Update Project function to populate the % Complete field with the "expected" data
c. Use the following formula in Text2:
Text2=[% Complete]-[Text1]
Unless I'm missing something, the Text2 field now has your % variance.
Now for my question. What exactly is the "% planned" you are looking for? Isn't that what you are calling the output of the Update Project function?
With regard to the % Complete field and the Actual Duration fields, they are interlocked by Project. If the user enters a value in one, Project calculates the other. So whatever value your PM enters for % Complete, you will see a calculated value (simple linear relationship) in the Actual Duration field. That's how the actual duration data is obtained for the formula I cited in my original response.
Just as an aside, variance is normally based on the current plan versus the baseline. There are a number of built-in variance fields already available in Project (e.g. start variance, finish variance, SV, SV%, etc.). Have you considered using one of those?
John