Question

I’ve been running an excel export function with .xlsx files. Occasionally when loading an excel file I use the System.Runtime.InteropServices.Marshal.BindToMoniker() method. When the file in question is not open, but exists, i get the following results:

Excel will start, but the workbook will not load, and neither will any worksheets. Excel appears blank.

When opening the file outside of the program that performs the exporting, it loads in exactly the same way. Excel is open, it says Microsoft Excel at the top of the window, but there are no visible sheets. Excel looks like there is nothing open at all.

Going into the options also suggests that there are no workbooks open. The file definitely has content though, as I can see when I open it in Notepad++ The document has enough detail for me to see that there are sheets in the workbook, but nothign shows up.

I’m not sure how to prevent this corruption from happening programmatically, or how to fix it. Any suggestions or thoughts would be appreciated!

To avoid the problem I never use BindToMoniker on closed Excel files (by checking whether the file is locked or not, if it’s unlocked, I just use the open function)

Here is the code that runs when i get this problem. It will only happen if the file exists and is not open:

    Public Function OpenExcelFile( _
    ByRef pobjExcel As Excel.Application, _
    ByRef pwkbWorkBook As Excel.Workbook, _
    ByVal pstrFileName As String) As Boolean 

…

pwkbWorkBook = BindToMoniker(pstrFileName)
            pobjExcel = pwkbWorkBook.Parent
            pobjExcel.Visible = True 'Temp; I use this to see the state of the file

Answer 1

Could it be that the workbook has been hidden? On the view tab, if Unhide is enabled you can reveal your hidden workbooks.

Also, if you think a workbook should be visible you can reveal it by updating the Windows visible property.

pobjExcel.Windows(workbookName).Visible = True