Problem with Infrastructure Update

[Sheila Murphy]

We loaded the infrastructure update a few days ago, both on the server and
for those clients use Project 2007 Pro. One of the Project Pro user's found
a problem yesterday that appears to be a bug, or at least a difference in
behaviour from the software before the update.

First some background. To level several projects at once, we multi-select
in PWA and select the edit button. This creates a master project in Project
Pro. We run leveling and then run a macro that I wrote called
SaveAndPublishSubProjects that goes through all the subprojects, opens them,
saves them, publishes them and closes them. Then, we close the master
project without saving.

Now for the problem. We noticed that what was published didn't include our
leveling changes. We checked the queue information on the server and saw
that it had published, but no save had been sent to the server. After some
debugging, I found that while the script was running that ActiveProject.Saved
was true, indicating that there had been no changed since the file was last
saved. But, there had been changed, just they were done from the master
project and the newly opened window to the subproject does not seem to know
about these changes. There were 20 subprojects, 9 of which did not change
during the leveling and 11 that did. 2 of the 9 think they are modified
(even though they haven't been) and the remaining 18 think they are not
modified.

I went back to a machine that did not have the Infrastructure Update loaded
and it appears there that the Saved property is correct, or at least fails on
the side of saving, as all the projects think they have been modified and
save.

I tried to workaround the problem by writing a macro that would open the
projects for all the subprojects prior to the leveling, but then I started
seeing crashes when it was trying to close the schematics in the original
script (which had been modified to just activate and not open). I also tried
making some other change to the project from the SaveAndPublish script to
force it to save, but it looks like it only saved the change that I made and
not the leveling changes. So, I'm guessing there are other flags indicating
what has changed to know what to save and those aren't set right either.

Has anyone else seen this problem and is there a way to fix it or workaround
it? If not, is there a way to remove the Infrastructure Update and go back
to SP1 without reloading 2007 Project Pro and SP1?

Sheila

 

[Jack Dahlgren]

Sheila,

From what I know about the infrastructure update, it may have made some
behavioral changes, but from what your description implies is that you should
be able to work around them. If you can post the code in your SaveandPublish
macro it would be a lot easier to identify the problems and let you know how
to fix them.

-Jack Dahlgren

 

[Sheila Murphy]

Here is my macro. By the way, I had one version (lost it during one of the
mentioned crashes) that compared subproj.SourceProject.Saved and
ActiveProject.Saved and they didn't match.

Sub SaveAndPublishSubProjects()

Dim subproj As Subproject
Dim myproj As Project
'go through all the subprojects in the file
For Each subproj In ActiveProject.Subprojects
'open them all in turn
FileOpen (subproj.Path)
Set myproj = ActiveProject

If (Not (ActiveProject.NumberOfTasks = 0)) Then

'when open do something to the file
If (FileSave) Then
Publish
End If

End If

FileClose

Next subproj

End Sub

 

[Sheila Murphy]

Anyone have any suggestions of how to fix or workaround this? Is there a way
to save the subprojects from the master project, without actually opening
windows for them? It somehow happens if you close the master and tell it not
to save the master, it prompts to save each of the subprojects, so is there a
way I can do that via VBA?