PRJ: Hidden and Windowless Projects Hang ProjectAnalyzer Macro (139836)



The information in this article applies to:

  • Microsoft Project for Windows 4.0
  • Microsoft Project for Windows 95 4.1

This article was previously published under Q139836

SYMPTOMS

When you use the ProjectAnalyzer macro to analyze a windowless or hidden project, the macro may hang (stop responding). You do not receive an error message about this macro failure.

WORKAROUND

To work around this problem, make sure the project to be analyzed is associated with a project in an unhidden window.

To unhide a project, use the following steps:

  1. On the Window menu, click Unhide.
  2. Select the project to be shown and click OK.
To display a windowless project in a window, use the following steps:

  1. On the Window menu, click New Window.
  2. Select the project to be shown and click OK.

STATUS

Microsoft has confirmed this to be a problem in the versions of Microsoft Project listed above.

MORE INFORMATION

The ProjectAnalyzer macro displays a list of open nonconsolidated projects to choose from, and then provides information about the selected project. If a project is selected that is not associated with an unhidden window, the macro will hang. A project that is not associated with an unhidden window is not listed at the bottom of the Window menu; it has only hidden windows, or is windowless. A list of hidden windows can be seen by clicking Unhide on the Window menu. A list of all nonconsolidated projects, including hidden and windowless ones, can be seen by clicking New Window from the Window menu.

A windowless project is a project that is open, but is not associated with any window. For example, when a consolidated project is opened, any source project that is not already open will be opened as a windowless project. Also, when you open a project that contains links from another project, if you click Yes to the Reestablish Links? message, the source project will be opened as a windowless project.

NOTE: A consolidated project cannot be directly analyzed by the ProjectAnalyzer macro, but its source projects can.

REFERENCES

For more information about the ProjectAnalyzer macro, see the Samples.wri file in the directory where Project was installed.

Modification Type:MajorLast Reviewed:10/7/2003
Keywords:kbbug kbcode kbpending KB139836