Toevoegen van code via een macro.

Sub naardeknoppen()
  For Each oObj In ActiveSheet.OLEObjects
    If InStr(oObj.Name, "Button") > 0 Then ActiveWorkbook.VBProject.VBComponents("Sheet1").CodeModule.AddFromString "Private Sub " & oObj.Name & "_Click()" & vbCr & " MsgBox " & Chr(34) & oObj.Name & " is aangeklikt" & Chr(34) & vbCr & "End Sub"
  Next
End Sub

Sub start()
  ActiveSheet.Unprotect

  With Application.FileSearch
    .LookIn = ThisWorkbook.Path
    .Filename = "*.xls"
    Application.Caption = .Execute & " document(en) gevonden."
    For i = 1 To .FoundFiles.Count
      Sheet3.Cells(8 + i, 1) = Dir(.FoundFiles(i))
      With Sheet3
        For j = 1 To 3
          With .OLEObjects.Add("Forms.CommandButton.1", , , , , , , Sheet3.Columns(4).Left + Choose(j, 1, 50, 100), .Rows(8 + i).Top, 40, .Rows(8 + i).Height)
            .Name = Choose(j, "CopyButton", "OpenButton", "ClipButton") & (8 + i)
            With .Object
              .Caption = Choose(j, "Copy", "Open", "Clip")
              .Font.Size = 9
              .ForeColor = vbBlue
            End With
          End With
        Next
      End With
    Next
  End With

  NaarDeKnoppen
  ActiveSheet.Protect
End Sub

Sub CopyThisFile(ByVal nRow As Integer)
  MsgBox "CopyThisFile on Row " & nRow
End Sub

Sub OpenThisFile(ByVal nRow As Integer)
  MsgBox "OpenThisFile on Row " & nRow
End Sub

Sub ClipThisFile(ByVal nRow As Integer)
  MsgBox "ClipThisFile on Row " & nRow
End Sub

Sub NaarDeKnoppen()
  For Each oObj In Sheet3.OLEObjects
    If InStr("CopyButton*OpenButton*ClipButton", Left(oObj.Name, 10)) > 0 Then ActiveWorkbook.VBProject.VBComponents("Sheet3").CodeModule.AddFromString "Private Sub " & oObj.Name & "_Click()" & vbCr & Replace(oObj.Name, "Button", "ThisFile ") & vbCr & "End Sub"
  Next
End Sub

[B]Avoid the Variant Data Type[/B]

Avoid the use of the Variant data type whenever possible. Unfortunately, VBA is not a strongly typed programming language.
Therefore, you can simply declare variables without specifying their data type and VBA will create these variables as Variants. 
The main reasons not to use Variants are as follows:

 * Variants are very inefficient This is because internally, a Variant is a very complex structure designed to hold any data type 
in the VBA programming language. Variant values cannot be accessed and modified directly as can fundamental data types 
such as Long and Double. Instead, VBA must use a series of complex Windows API calls behind the scenes whenever it 
needs to perform any operation on a Variant.

 * Data stored in a variant can behave unexpectedly Because Variants are designed to hold any type of data, the data type 
that goes into a Variant is not necessarily the data type that will come out of it. When accessing the data in a Variant, VBA 
will attempt to coerce the data into whatever data type it thinks makes the most sense in the context of the operation. If you 
must use Variants, always explicitly cast them to the data type you want when using their values.

[B]Beware of Evil Type Coercion[/B]
Evil Type Coercion (ETC) is another symptom that results from VBA not being a strongly typed programming language. 
ETC occurs when VBA automatically converts one data type to another completely unrelated data type. The most frequent 
examples are Strings that hold numbers being converted to Integers and Booleans being converted to their String equivalents. 
Don't mix variables of different data types in your code without using the explicit casting functions (CStr, CLng, CDbl and so on) 
to tell VBA exactly how you want those variables to be treated.