Bugged behavior in Listview ActiveX Control

Hi guys, I making and spreadsheet that with a Listview Activex Contron on a sheet.
However, I am experiencing some bugs with this control.

First of all, I am not able to add columns headers. I am using the same code that actually work when adding header in a Listview that is in a userform, but I get an error: "Invalid property value" when trying to do the same with the list view activex control in a sheet.

Here is the code:

Sub Configure_Activex_Listview()
  
    With Sheets(1).ListView1
        .Gridlines = True
        .HideColumnHeaders = False
        .View = lvwReport
        .ColumnHeaders.Add Text:="Column 1", Width:=50
        .ColumnHeaders.Add Text:="Column 2", Width:=50
    End With
End Sub

Beyond that, when the code start, excel seems to create a second activex control on the screen, that only goes out if I delete the original control. I attached an image of this bug.

Bug.JPG




And it is even more strange because it also happen if a manipulate an userform that has nothing to do with the listview itself.

I created a file where you can see this behavior and also see that the same code will run when applying to a listview in a userform: https://drive.google.com/file/d/0B6w...ew?usp=sharing

I hope any of you could help me with this, because first I have started making this application entirely on userforms but then I decided to change it to activex controls, but now I am almost thinking about going back to the userform approach.

Originally Posted by shg

I think you would get pretty consistent recommendations here to go back to userforms. ActiveX controls on worksheet are very buggy.

I decided to place activex controls directly on the sheet because I am planning to make a app that does not look like Excel at all and using sheets it is also possible to use a bigger variety of shapes and other good lloking elements than in userforms.
I was also having some problems with userform positioning and how to predict how it would like in different resolutions.

But I guess that maybe the apparent advantages of using activex controls are not worth, so I may go back to the userform approach.