Hi,
I don't think there is a clean simple way,
covering all possibilities, such as merging tables,
splitting tables, deleting tables, adding tables.
Not to speak of nested tables.
Unless you store all information about the tables
at a given point in time e.g. in a logfile,
and check afterwards, whether anything has changed.
However, within one single macro, or on a larger
scale in a (modeless) userform, you may first
assign each table to a table object and get an
error 5825, object deleted, in case it's gone.
Like this:
Sub test301()
Dim oTbl() As Table ' table object
Dim iTbl As Integer ' counter
ReDim oTbl(ActiveDocument.Tables.Count)
For iTbl = 1 To ActiveDocument.Tables.Count
Set oTbl(iTbl) = ActiveDocument.Tables(iTbl)
Next
oTbl(4).Select
Selection.Cut
oTbl(4).Select ' error 5825
End Sub
I think, you can take care of
an error handler yourself, otherwise
ask again.
Greetings from Bavaria, Germany
Helmut Weber, MVP
"red.sys" & chr(64) & "t-online.de"
Word 2002, Windows 2000
Alok - 23 Dec 2004 05:43 GMT
well i had that idea as a backup option.
thanks anyway
Thanks,
Alok
> Hi,
> I don't think there is a clean simple way,
[quoted text clipped - 33 lines]
> "red.sys" & chr(64) & "t-online.de"
> Word 2002, Windows 2000