> Dealing with tables is *always* slow. The best method is to insert the cell
> contents as plain text, with "columns" separated by tabs and with "rows"
[quoted text clipped - 48 lines]
> > Thanks,
> > Adam
Hi ACFalcon,
What is oDT? Another Table?
What oDRW? A row?
What's going on here:
> For Each oDRW In oDT.Rows
> With oWT.Rows(c)
You seem to loop over each row,
and in addition to loop over rows(.rows.count), but row 1.
To delete the first two cells of every row
except the first row,
one could try:
Sub Test6789()
Dim oCll As Cell
ActiveDocument.Tables(1).Columns(1).Select
selection.MoveRight Unit:=wdCharacter, _
Count:=1, Extend:=wdExtend
selection.start = selection.Cells(3).Range.start
'selection.Cells.Delete
ActiveDocument.Tables(1).Columns(1).Select
selection.start = selection.Cells(2).Range.start
For Each oCll In selection.Cells
oCll.WordWrap = True
' some more properties to be set
Next
End Sub
It seems you can't set wordwrap to the selection.cells.collection
In tables ranges are sometimes,
not so say most often, slower than the selection.
See:
http://tinyurl.com/y436j7

Signature
Greetings from Bavaria, Germany
Helmut Weber, MVP WordVBA
Win XP, Office 2003
"red.sys" & Chr$(64) & "t-online.de"
ACFalcon - 22 Nov 2006 14:21 GMT
oDT is a .NET Datatable and oDRW is a .NET Datarow. They are not slowing
down the process, because if I remove the editing of the word table
everything runs very quick.
> Hi ACFalcon,
>
[quoted text clipped - 34 lines]
> See:
> http://tinyurl.com/y436j7
Helmut Weber - 22 Nov 2006 20:27 GMT
Hi,
>oDT is a .NET Datatable and oDRW is a .NET Datarow.
>They are not slowing
>down the process, because if I remove
>the editing of the word table
>everything runs very quick.
of course, the mere existence of them does
no harm, but what you do with them...

Signature
Greetings from Bavaria, Germany
Helmut Weber, MVP WordVBA
Win XP, Office 2003
"red.sys" & Chr$(64) & "t-online.de"