Replies

Yes, thanks Andrew. The registry update fixed the problem!

I have determined that the problem only occurs when the document is checked out from SharePoint. If I leave SharePoint out of the loop, or if I open the document from SharePoint as Read-Only, the bookmark cross-references work fine. Are there any SharePoint/Word 2007 users out there who are having the same problem, or know a solution/workaround? I have tried substituting hyperlinks for the bookmark cross-refernces and the same bogus pop-up error occurs.

Yes, thanks Jefferson. That was exactly what I needed to search for the acronyms!

You could try a wildcard search. For this, you need to use the More button to expand the Find dialog, if it is not already expanded, check the “Use wildcards” box, and use a pattern similar to the following:

Code:

([A-Z]{2}*)

That specifies an opening parenthesis, two capital letters, then 0 or more of any characters, then a closing parenthesis. The backslashes are to indicate that the parentheses should be interpreted literally, rather than interpreted as a grouping.

Does that match what you need?

Unfortunately, when you next want to do a case-insensitive search, you will need to uncheck the “Use wildcards” box. If it gets to be too much of a headache, you could create a macro to do the search and clear the box for the next one.

Thanks Hans and Jefferson. When I unchecked the Smart Cut and Paste option, the problem went away.

Well at least it worked like a charm from my home computer last night. Now that I’m at work, I’ve noticed that the document number is being cut off at the first hyphen (Title property CTIS-MIN-09-0001 results in CTIS.doc in the File Name box of the Save As dialog). Strange that it would work on one PC but not another (same versions of Word on each). I noticed in the MVPS article (which you supplied the link for) that delimiters such as underscores cause problems. I guess hyphens fall into this category as well. Is there any good workaround that would involve no extra work for the user?

Worked like a charm as usual, Hans! I pasted the inner 4 lines of your macro to the end of the userform’s CommandButton code. The replacement of the value of the Title file property is completely transparent to the user. THANKS!

Hans,
Gee, Hans, that actually worked! Thanks a lot! I was a little confused at first by the ‘Code to execute first time goes here’ until I realized I was supposed to put the code to open my userform there. With your code, what I have is a simulation of SharePoint handling a Word template. Once the user is through completing the userform, saves, re-opens, and doesn’t see the userform again, it will appear as if the document he created was based on a template, when actually it is only a copy of a .doc but with a neutered AutoOpen. (I am forced to deny the users checkout privileges to prevent them from overwriting the “template” upon check in, so I have them open a read-only copy.)

Thanks, Stuart for the tip about WebDav. I’ll talk to my systems people and see if we can implement it.

Thanks, Hans. The Microsoft article is beyond my ability to understand and my authorization to implement it even I could understand it. I don’t see how using a .doc instead of a .dot solves the problem because the .doc would also be in danger of being overwritten. What I desire is for SharePoint to maintain my template, and when a user opens it, he gets a .doc separate from the template but based on it, as in Word.

Thanks a lot, Steve, for the macro that assigns Keep WIth Next to all sentences ending with a colon. It’s going to get a lot of use in the lengthy user manuals I edit. A real time-saver for sure!

Thanks, Jefferson. The method you described is what I currently use. It’s fast and easy, but I was wondering if there was a macro that could allow me to be even lazier

I want to jump in here to comment on the problem you mentioned where all the entries of the TOC display a single random page number. This has been a recurring problem for our office so frequently that I have resorted to inserting the following AutoOpen macro into every document I edit (we are using Word 2003 SP2). This macro update all the fields, then positions the insertion point at the beginning of the document.

Sub AutoOpen()
‘
‘ UpdateTOCatOpen Macro
‘ Macro recorded 10/2/2006 by your name
‘
Selection.WholeStory
Selection.Fields.Update
Selection.MoveUp Unit:=wdLine, Count:=1
End Sub

Thanks again, Hans. The LockPPT macro did the trick! The writing team will be ecstatic when I show them.

When I lock the slides they don’t update when I try to do so. But with up to 50 slides in a document, visiting each slide and locking it would be burdensome, that is unless there is a macro that can do this.