I have been fighting with an Excel 2007 problem for several days now. Below is a listing of all facts I can think of that might be relevant:

1. *IDetailSheet* is a class declared in the VBA project with several methods, and which throws an error in its Class Initializer so that it cannot be instantiated (making it abstract).
2. *Option Explicit* is set in all modules.
3. Ten worksheets in the VBA project *implement* *IDetailSheet* and compile cleanly (as does the entire project).
4. *CDetailSheets* is a class declared in the VBA project that wraps a Collection object and exposes the Collection object as a Collection of *IDetailSheet*. It also exposes some additional methods to perform certain methods of *IDetailSheet* on all collection menmbers.
5. In its Class initializer (called from the *Workbook*\_ *Open* event handler and assigned to a global variable), *CDetailSheet* executes the following code to populate the private collection *DetailSheets*: 

```
Dim sht as EXCEL.WorkSheet
For Each sht in ActiveWorkbook.Worksheets
  If TypeOf sht is IDetailSheet Then
    Dim DetailSheet as IDetailSheet
    Set DetailSheet = sht
    DetailSheets.Add DetailSheet, DetailSheet.Name
  End If
Next sht

```
6. In certain Ribbon call-backs the following code is run: 

```
   If TypeOf ActiveWorkbook.ActiveSheet is IDetailSheet Then
      Dim DetailSheet as IDetailSheet
      Set DetailSheet = ActiveWorkbook.ActiveSheet
      DetailSheet.Refresh  *[correction]*
   End If

```
7. All ActiveX controls have been removed from the Workbook, after having been identified with other stability issues (There were a few dozen originally). A Fluent Interface Ribbon has been created to replace the functionality originally associated with the ActiveX controls.
8. There is a Hyperion add-in from the corporate template, but it is not used in this workbook.

When all is said and done, the following symptom occurs when the workbook is run:

* Any number of instances of IDetailSheet are recognized in the CDetailSheets Initializer by **TypeOf Is**, from 1 (most common) to occasionally 2 or 3. Never zero, never more than 3, and most certainly never the full 10 available. (Not always the same one, though being near the front of the set seems to increase likelihood of being recognized.)
* Whichever instances of IDetailSheet implementation are discovered in the CDetailSheets initializer (and as near as I can determine, only such instances) are also recognized by **TypeOf ... Is** in the Ribbon call-back.

Can anyone explain why most of the **TypeOf ... Is** operations are failing? Or how to fix the issue?

I have resorted to manually creating v-tables (i.e. big ugly *Select Case ... End Select* statements) to get the functionality working, but I actually find it rather embarrassing to have my name beside such code. Besides which, I can see that being a future maintenance nightmare.

Thinking that it might be a stale p-code issues, I went to the extent of deleting the Project.Bin file from the expanded XLSM zip, and then manually importing all the VBA code back in. No change. I also tried adding the project name to all the usages of *IDetailSheet* to make them *miFab.IDetailSheet*, but again to no avail. (*miFab* is the project name.)