How to write your own Excel VBA code and how to use the Object Browser to obtain such code

The object browser will not provide code as such... it simply helps you figure out what code to write. For example if you check a worksheet object, you find that it has properties such as Name, so then you know that to change the name you would say ws.Name = xxxxxx. Unfortunately it will only give you info that helps write code, not actually build that code for you.

Instead of, or in addition to the object browser, I tend to use this help file (https://msdn.microsoft.com/en-us/lib.../ff194068.aspx ) as a gateway to the help files for the different objects, methods, and properties in Excel's object model.

I think it depends on your background and if you have any programming experience. Recording a macro is a good way of getting the basic code but it is limited. It records exactly what you do, it's slow and it's inefficient. And, typically, it records one pass when you might want a loop.

So, for example, you might record a macro that puts a formula in lots of cells in a column. You can do that in one step without selecting anything. But that's not the way the macro recorder will show you.

I learnt by reading lots of books, dissecting code that I found or was given, and then trying to apply and adapt the code. Nowadays, if I need to find out how to do something that I have not done before, I will Google it. Usually, I find what I want and I can adapt it. Sometimes, I don't find what I want, or I find what I think I want but I can't make it work. Then I ask questions of others and hope that someone can help. More often than not, they can and do.

With regard to the Object Browser, I rarely use it and I don't always find it intuitive. Knowing Excel, you have to work down the hierarchy ... the Excel Application works with Workbooks, which contain Worksheets, Chart Sheets, etc. A worksheet contains cells, or ranges. A cell will contain a value or a formula and can be formatted ... very simplistic view

I still record macros to get the basic structure for code I don't often use. And I think it's one of the best ways of learning.

Depending on your learning style, it can be good to set yourself a task and record each step as you complete the task manually. Then you can review the code and adapt it for speed, efficiency and to make it generic. I guess you're doing that to some extent so all I can say is keep at it. And maybe buy yourself a good book. I'd recommend anything by John Walkenbach.