Replies

Thank you all for the good ideas. In each case, it sounds like there is a second table. That is a our workaround but I was curious if there was a case for one, dynamic table, since we don’t know which tables are going to expand or by how much.

Have you tried using the Table ‘header row’ property (Table Tools>Layout>Properties>Row)? Do note that there is no facility for adding anything like “(continued from previous page)”.

Thanks for the reply. I knew about that but was hoping there was something I missed.

I got around a little of this by reading the 2003 version’s RTF and 2007’s XML to get a list of revision authors. For our large, marked up documents, it was taking 45+ minutes to use conventional For loops just reading the Revisions to compile an author’s list; now it’s trivial, perhaps as long as 10 seconds. I still have the overhead of reading the revisions.

Thanks! I like getting confirmation that the problem is actually an exception to the rule. Which segues to the next question. For Each Next is slow enough as it is, a For Next is even slower. In documents with a sufficiently large number of revisions, this process takes forever. Is there a way to get that Revision information into a memory structure, something like Revision.ToList() kind of thing?

Thanks for the code! Perhaps not the ideal solution but it addresses it.

Thanks! That is good to know. But that’s the very reason I want to find them programmatically: We shouldn’t be having direct-formatted modified named styles. It sounds like there is no way to programmatically find these deviations?

We have Office 2007 with 64 Bit Windows 7. MODI doesn’t work with that, correct? Is there workaround, or replacement?

My mistake. Apparently you shouldn’t mix old and new controls in the same form.

Delete that offending With section and the line “Selection.Borders(wdBorderVertical).LineStyle = wdLineStyleNone”.

wdBorderVertical is modified three times. The two With sections changing it are identical (so only the first is needed). While the other line changes the LineStyle, it would have been changed back later. Therefore, the last two references aren’t needed.

Could you restate the problem in anothe way or more clearly?

Rethinking the approach a little for Word 2007+, if you made it a content control, had a content control in the text box, or used a Text box that already had a content control in it, you could use the Document’s ContentControlOnEnter event.

Thanks for the confirmation!

How about this (with only one uncommented Delete statement each time, and manually deleting all the lines before each run)? Only the last case deletes all the lines.

Code:

 
Public Sub TestLines()
On Error GoTo MyErrorHandler
 
‘Sets up a lot of lines
Dim i As Long
For i = 1 To 300
     ActiveDocument.Shapes.AddLine 10, i * 2, 2000, i * 2
DoEvents
Next
 
Dim myShape As Shape
For Each myShape In ActiveDocument.Shapes
     ‘myShape.Delete
 
DoEvents
Next
 
Dim j As Long
For j = 1 To 300
     ‘ActiveDocument.Shapes(j).Delete
DoEvents
Next
 
Dim k As Long
For k = ActiveDocument.Shapes.Count To 1 Step -1
     ‘ActiveDocument.Shapes(k).Delete
DoEvents
Next
 
MsgBox “Shapes remaining: ” & ActiveDocument.Shapes.Count
 
Exit Sub
MyErrorHandler:
MsgBox “TestLines” & vbCrLf & vbCrLf & “Err = ” & Err.Number & vbCrLf & “Description: ” & Err.Description
End Sub

Thanks! Adding the widths of the previous cells was the missing detail. It’s too bad that this information isn’t already in the table structure.

That’s my point. This is finding the occurrence within a word. Can anyone confirm this is a bug, or seen it before, or have a workaround?