View Single Post
 
Old 10-02-2013, 12:33 PM
Charles Kenyon Charles Kenyon is offline Windows Vista Office 2010 32bit
Moderator
 
Join Date: Mar 2012
Location: Sun Prairie, Wisconsin
Posts: 9,530
Charles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant futureCharles Kenyon has a brilliant future
Default

Quote:
Originally Posted by moggymiaow View Post
On further investigation, the problem is when the autotext entries contain form fields, which most of them did, those without form fields could be seen, those with cannot. A bug which has been fixed in word 2007 obviously.The only way I could think to get around this would be to have an exteral file and store the entries in book marked areas and copy and paste, however it was not a solution that I wanted to go with and so have had to restrict what can be done with the document if the user is using word 2000 (some users do have 2007)
There is no compatibility pack allowing Word 2000 to open .docx files. Even with that I doubt this would work.

I suspect that your AutoText entries included the new form fields (Content Controls) rather than legacy form fields. These new fields are the default ones on the Developer Tab. Greg Maxey has a free Add-In that gives easier access to the legacy form controls. Add Classic FormField Controls to Ribbon

Also, Greg has another Add-In that makes it easier to use and organize AutoText in Word 2007. Building Blocks & AutoText

AutoText, back to Word 97, can hold form fields, but non-ribbon versions of Word do not know what to do with Content Controls.

Automated Boilerplate Using Microsoft Word
Reply With Quote