Question: Below is a code to merge multiple workbooks into a single workbook. However, the files that are being extracted from the local folder comes up incomplete once the process is done. My guess is the workbooks/files in that local folder far exceeds the range that's in the code.

How do I extend the range, preferably "unlimited" or to the maximum limit of excel to transfer and combine the workbooks as much as possible?

Below is the code that I use.

Please advise and our help is much appreciated.

Vincent

```
Sub Merger()
Dim bookList As Workbook
Dim mergeObj As Object, dirObj As Object, filesObj As Object, everyObj As Object
Application.ScreenUpdating = False
Set mergeObj = CreateObject("Scripting.FileSystemObject")

Set dirObj = mergeObj.Getfolder("C:\Users\Vincent\Desktop\856")

Set filesObj = dirObj.Files
For Each everyObj In filesObj
Set bookList = Workbooks.Open(everyObj)

Range("A2:IV" & Range("A65536").End(xlUp).Row).Copy

ThisWorkbook.Worksheets(1).Activate

Range("A65536").End(xlUp).Offset(1, 0).PasteSpecial

Application.CutCopyMode = False
bookList.Close

Application.DisplayAlerts = False

Next
End Sub

```

Answer: 
Mixing the code for your gradle plugin with the project code the plugin is supposed to help build is probably a bad idea. 

You should check out the gradle documentation on [organizing your build logic](https://docs.gradle.org/current/userguide/organizing_build_logic.html) and specifically I would have probably started by sticking your plugin source in the [buildSrc directory](https://docs.gradle.org/current/userguide/organizing_build_logic.html#sec:build_sources). 

If you put your plugin source in a directory called `buildSrc` as per the documentation above, it will be automatically compiled and included in your build classpath. It will also not be deleted when you clean your project. All you really need is the `apply plugin: x` statement. 

It should be noted that even though `buildSrc` is convenient, it is still there for the development phase of your plugin. If you intend to use the plugin more often, in more places, or otherwise share it, it is probably good to actually build a jar with the plugin.
It is an old question , but for the new visitors: you can build the plugin code while you build the code. there can be even a parent project that build all the plugins.
please check [this answer](https://stackoverflow.com/questions/35302414/adding-local-plugin-to-a-gradle-project)