Yes, but keep this very important fact in mind....Word is NOT Excel.

They use completely different object models.

Excel is cells...and frankly ONLY cells.

Word is text, and table cells are special paragraphs of....text. They are NOT cells....really. Yes, I know we try and pretend they are Excel-like cells, but they are not really.

Here is one way to see things.

Yes, you can, via code select a column, but you can not - repeat NOT - make a range object of a column. Ever. In Excel you can make ranges of cells in a column, but in Word you never can.

Using your logic that you will ignore Column 1, let's work through something.

row_1 = B
row_2 = Textxxxxx
row_3 = ""
row_4 = ""
row_5 = text2
[vba]Option Explicit
Function CellText(oCell As Cell)
CellText = Left(oCell.Range.Text, _
Len(oCell.Range.Text) - 2)
End Function
Sub MergeMe()
Dim oTable As Table
Dim oCell As Cell

Set oTable = ActiveDocument.Tables(1)
For Each oCell In oTable.Columns(2).Cells
If CellText(oCell) = "" Then
oCell.Merge Mergeto:=oTable.Cell(oCell.RowIndex - 1, _
oCell.ColumnIndex)
End If
Next
End Sub[/vba]Let run through.

It works on row_1. There is text - Celltext(oCell) is not "". So it continues.
It worlks on row_2. There is text - Celltext(oCell) is not "". So it continues.
It works on row_3. There is no text. It merges that cell to the one above.

It works fine.

It works on row_4....................

EXcept row_4 is now the row with Text2! Repeat, it is the last row. It is NOT the row with "1.3" in Column C.

Check this yourself manually. Select the cells with "Text1xxxx" and the blank cell below it, but just the one blank cell. Now merge them.

They merge and column C row 2 now has 1.1 and 1.2 inside the cell. Ditto for Column A.

How many rows has Column B? FOUR.

However, from the perspective of VBA, it does not have.....any. Rows is simply not a property of Columns.

Try using IntelliSense on: ActiveDocument.Tables(1).Columns(2).

You can not Range or Rows, because columns do NOT have either a Range or Rows property. Why? Because you can merge them.

So tell me. if you merge Cell(2,2) and Cell(3,2) - vertically - is the new cell row 2....or row 3? Since VBA has no idea either, it shrugs and simply refuses to deal with them.

Which is why, in the code above, yes, it merges the first iteration, but NOT the second, because "the object has been deleted".