VBA VBE对象.Saved布尔属性异常：真假判断同时成立？

This is a quirky behavior tied to how document modules (like ThisWorkbook or Sheet1) handle the Saved property, combined with how accessing the VBE object model interacts with Excel's workbook modification tracking. Let's break this down:

The Root Cause #

For document-based VBComponents (as opposed to standard modules), the Saved property doesn't represent the component's own saved state—it's a proxy for the workbook's Saved property. The problem comes when you read this property multiple times in quick succession:

• The first time you read VBComp.Saved, it returns the workbook's current saved status (which is True for a new, unmodified workbook).
• But accessing the VBE object model programmatically can trigger Excel to mark the workbook as "modified" (even if you didn't change anything). This flips the Saved property to False for subsequent reads.

In your code, you're reading VBComp.Saved three times:

1. When assigning to IsSaved
2. When checking CStr(VBComp.Saved) = "True"
3. When printing the value to the Immediate Window

By the time you get to your conditional checks, the Saved property has already flipped—but your IsSaved variable still holds the original value. The inconsistent execution of both conditionals happens because of how VBA handles volatile COM property access for these specific components.

The Fix: Read the Property Once and Reuse It #

The solution is simple: read the Saved property once, store its value in a variable, and use that variable for all your checks. This avoids the value flipping between reads.

Here's your corrected code:

Sub ListModules()
    Dim VBComp As Object 'VBComponent
    For Each VBComp In Application.VBE.ActiveVBProject.VBComponents
        Dim IsSaved As Boolean
        ' Read the Saved property ONCE and store it
        IsSaved = VBComp.Saved
        
        Debug.Print vbNewLine; VBComp.Name; " saved? "; IsSaved; " ("; TypeName(IsSaved); ")"
        
        If Not IsSaved Then
            Debug.Print VBComp.Name; " is not saved"
        End If
        If IsSaved Then
            Debug.Print VBComp.Name; " is saved"
        End If
    Next VBComp
End Sub

Why This Works #

By storing the value in a local variable, you're capturing the exact state at the moment you read it. Subsequent checks use this static value instead of re-reading the volatile Saved property, which prevents the inconsistent results you saw.

Additional Notes #

• This behavior only affects document modules (ThisWorkbook, SheetX). Standard modules will behave as expected with their own Saved property.
• Remember to enable trust access to the VBA project object model (as you noted) to run this code without errors.

内容的提问来源于stack exchange，提问作者mwolfe02