The Problem (Q-score 3, ranked #155th of 303 in the Excel VBA archive)
The scenario as originally posted in 2014
So I’m working on a project and I’m trying to get my VBA code to draw down the formula that’s in cell M3 all the way down to the end of the data set. I’m using column L as my base to determine what the last cell with data in it is. My formula is a concatenate of two cells with a text comma in-between them. So in excel my formula is =G3&”,”&L3
I want excel to draw down this formula so in cell M4 it would be =G4&”,”&L4
Cell M5 would be =G5&”,”&L5 and so on.
My code looks like:
Range("$M$3").Formula = Range("G3") & (",") & Range("L3")
Dim Lastrow As Long
Application.ScreenUpdating = False
Lastrow = Range("L" & Rows.Count).End(xlUp).Row
Range("M4").FormulaR1C1 = Range("G4") & (",") & Range("L4")
Range("M4").AutoFill Destination:=Range("M4:M" & Lastrow)
ActiveSheet.AutoFilterMode = False
Application.ScreenUpdating = True
My output is simply pulling down the text values from cell M3 all the way down to the end of the data set. I’ve searched around for several hours trying to look for a fix, but can’t seem to find one that is trying to accomplish what I’m going for.
Why community consensus is tight on this one
Across 303 Excel VBA entries in the archive, the accepted answer here holds solid answer (above median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — solid answer (above median) (+13)
Verbal answer — walkthrough without a code block
Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.
It’s a one liner actually. No need to use .Autofill
Range("M3:M" & LastRow).Formula = "=G3&"",""&L3"
When to Use It — classic (2013–2016)
Ranked #155th in its category — specialized fit
This pattern sits in the 96% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.
What changed between 2014 and 2026
The answer is 12 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.