Importing a report through the enabler4excel add-in
Readability &amp; Maintainability

Use indentation to make control-structures easier to understand and read.
Some variables are all lower-case, some are camelCase, some are PascalCase. OCD is unhappy :( Use a consistent naming convention. I'd recommend camelCase. Either way, choose one and stick to it
ButtonClick1 is a rather non-descriptive name
these &quot;random&quot; spaces before the third argument look strange. I assume they're not there in your own code, right?

Compartmentalization
You should be able to make your code into neat little compartments. Those are also known as &quot;methods&quot;, &quot;functions&quot;, &quot;procedures&quot;  or a handful of other names. All these separate paragraphs that have been mentioned in a comment already can almost be methods. Consider:
Set automationObject = FindEnablerAddin()
' [...]
Private Function FindEnablerAddin() As Object
    For Each addin In Application.COMAddIns
        If addin.Description = &quot;Enabler4Excel&quot; Then
            Set FindEnablerAddin = addin.Object
            Exit Function
        End If
    Next addin
    'FindEnablerAddin should be Nothing
End Function

This can be applied in other places as well. Note that I have used Exit Function to break the loop over all COMAddIns early. This may or may not help with performance noticeably. It usually avoids work, so you should do it.
Performance &amp; Nitpicks

You can usually significantly increase performance by turning of Events, Calculation and ScreenUpdating in Excel. Don't forget to turn them back on, even if your code falls into an error state.
Working on the Workbook directly is slow. Then again this looks like you don't have much of a choice here
Instead of If Result = False Then you can use If Not Result Then. This is cleaner and avoids the potential for confusion about assignment and boolean comparisons