PRB: 'For Each' with 'Delete' Doesn't Work for DAO Collections

MORE INFORMATION

Steps to Reproduce Behavior

1. Start a new project in Visual Basic. Form1 is created by default.
2. Add the following code to the Form1_Load procedure:

      Private Sub Form_Load()
         Dim DB As Database
         Dim MYdbSystemObject As Long
         Dim I
   
         MYdbSystemObject = &H80000000
         On Error Resume Next
         Kill "TestDB.MDB"
         On Error GoTo 0
         Set DB = DBEngine.Workspaces(0).CreateDatabase("TestDB.MDB",_
            dbLangGeneral)
         For I = 1 To 10
            Call AddTD(DB)
         Next
         Debug.Print DB.TableDefs.Count
         For Each TDObj In DB.TableDefs
            If (TDObj.Attributes And MYdbSystemObject) <> _
               MYdbSystemObject Then
            Debug.Print TDObj.Name ; " deleted"
            ' This test is to avoid the System tables supplied by Jet.
            ' These tables may not be delete from the collection.
            DB.TableDefs.Delete TDObj.Name
            End If
         Next
         Debug.Print DB.TableDefs.Count
      End Sub
   						

3. Add the following code to the General Declarations section of Form1:

      Sub AddTD(DB As Database)
         Static I As Integer
   
         I = I + 1
         Dim TD As New TableDef
         Dim FD As New Field
         TD.Name = "Table" & Trim$(Str$(I))
         FD.Name = "Field" & Trim$(Str$(I))
         FD.Type = dbInteger
         TD.Fields.Append FD
         DB.TableDefs.Append TD
         Debug.Print "Added Table "; TD.Name
      End Sub
   						

4. Start the program by choosing Start from the Run menu or by pressing the F5 key. The program lists the tables that it adds, but it only deletes the odd-numbered tables.
5. To get the code to work correctly, modify the For Each loop. Replace the For Each statement with the following two statements:

      For I = DB.TableDefs.Count - 1 To 0 Step -1
         Set tdobj = DB.TableDefs(I)