Thanks for the reply. It's appreciated. In the past, I was using the methodology you suggest, however, I ran into problems when the number of records in a DataSet exceeded the number of preset rows in the Word table, whereby rows had to added on the fly. This not only slowed the performance but also over-filled or over-ran other portions of the table. For example, the Word table has a section or rows for listing services or products and below those rows is the total amount for those products or services (like any other invoice). However, when additional rows have to be added, to list products, it overruns the total amount section. Here's a sample of the code:
With moWordDoc.Tables.Item(iTableNum)
Do While Not moAdoSql.EOF
RowCnt = RowCnt + 1
If RowCnt > .Rows.Count - iNumOfRowsBeforeInsert Then
.Rows.Add(.Rows.Item(RowCnt - 1))
End If
.Cell(RowCnt - 1, COL_date).Range.Text = VB6.Format(NullToString(moAdoSql.Fields("transaction_date")), gcFORMAT_ShortDate)
.Cell(RowCnt - 1, COL_desc).Range.Text = NullToString(moAdoSql.Fields("transaction_desc"))
.Cell(RowCnt - 1, COL_time).Range.Text = NullToString(moAdoSql.Fields("time_billed"))
moAdoSql.MoveNext()
Loop
End With
As a result, per Microsoft article, http://msdn.microsoft.com/en-us/library/aa537149(v=office.11).aspx, I'm trying to use the ConvertToTable method.
Any help is appreciated.