Q120026 - FilterEdit Method Loses Memory and Causes File Corruption

FilterEdit Method Loses Memory and Causes File Corruption

Q120026

The information in this article applies to:

Microsoft Project for Windows, version 4.0

SYMPTOMS

Using the Visual Basic for Applications FilterEdit method produces an out- of-memory error message. Saving a file after this error causes the saved file(s) to become damaged.

CAUSE

The FilterEdit method does not release memory in all cases. This problem occurs when you set the Create and Overwrite Existing parameters to False.

WORKAROUND

If you run the macro and set the Create and OverwriteExisting parameters to True, the macro runs without producing the out-of-memory message and will not damage your saved file(s).

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce Behavior

Enter the following macro into a new module:


      Sub OutOfMemory()

      For x = 1 to 150
         FilterEdit Name:="critical", TaskFilter:=True, _
         Create:=False, OverwriteExisting:=False, _
         FieldName:="critical", Test:="Equals", _
         Value:="Yes"
      Next x

      End Sub

From the File menu, choose Save. Save the file as BAD.MPP.

From the Tools menu, choose Macros. Run the OutOfMemory macro.

Once you encounter the out of memory message, you have to exit Microsoft Project to free the memory. If you save your file after this message, when you try to reopen the file, Microsoft Project reports the file is damaged.

Additional query words:

Keywords :
Issue type : kbbug
Technology : kbProjectSearch kbProject400