View Single Post
  #16 (permalink)  
Old 04-04-2008, 12:17 PM
ssanderlin's Avatar
ssanderlin ssanderlin is offline
EPMFAQ Founder/Owner
 
Join Date: Feb 2008
Location: Quakertown, PA
Posts: 171
Thanks: 0
Thanked 17 Times in 17 Posts
Default

Quote:
Originally Posted by agriffin View Post
There was no MSP_EpmProject_UserView table, but there was a MSP_EpmProject table. I looked in this table and both of those columns were set to 0 for project. All of the projects are set to 0 for these 2 columns.
MSP_EpmProject_UserView is a View, not a Table.

OK... So, that's fine. I didn't expect them to be 1, since ProjectRollupsAreStale is supposed to only be used for master project / sub project relationships and ProjectCalculationsAreStale is supposed to be set when the Calculation is set to Manual and the Project is published -- but I figured we should check

I'd like to try one more thing... I don't think it will work, but it's worth a try. In one of the projects, uncheck the Actual Costs are always calculated by Microsoft Office Project option in Tools>Options>Calculate. Then, see if the rollups calculate correctly when the PSI publishes.

I think it's obvious that the Project rollup is not being recalculated, but I'm not sure why -- according to the documentation, this should occur.

If my above suggestion does not resolve the issue, you may want to consider using the Project Pro Object Model to open, recalculate, and save the project before you call your Publish method... I don't believe the Server-Side Scheduling Engine is exposed through any interface, so I don't think you can resolve your problem by forcing it to calculate.
__________________
Stephen Sanderlin
Founder/Owner - EPMFAQ
VP of Technology - MSProjectExperts
Microsoft Project MVP

If you found this message useful, please click the Thanks button in the post!

This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly.
Reply With Quote