 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Applications / Word / October 2006Macro for table problems
Hi Everybody I've created a table specifying all the properties in Word for Mac 2004. Since I use the format for this particular table frequently, I've tried without success to create a macro for it. I create a macro, insert Table (2 columns x 1 row), go to Table Properties, tick Preferred Width box and specify width, specify Indent from Left, go to Borders and Shading and specify No Borders, but then find that the Preferred Width and Indent measurements have disappeared. If I do it in reverse order, and then tab Row, I also lose the ticked Preferred Width measurements. If I go through and complete the other specs, and go back to Table, the macro doesn't produce the required table, but seems to insert some properties of its own, like width of column. Since the original table appears in the document, I assume that its properties are valid. I'll be indebted for advice. Many thanks John One approach, and the one usually recommended for repeating tables: Forgot the macro (which will break in the next version, anyhow), and save your custom table as an AutoText (Select it, Insert | AutoText | New, I think). More info: http://word.mvps.org/FAQs/Customization/AutoText.htm (hit reload a few times in Safari, or use a different browser) I think Bend Word to Your Will may also have notes on this: http://word.mvps.org/mac/bend/bendwordtoyourwill.html > Hi Everybody > [quoted text clipped - 22 lines] > > John  SignatureDaiya Mitchell, MVP Mac/Word Word FAQ: http://www.word.mvps.org/ MacWord Tips: <http://word.mvps.org/Mac/WordMacHome.html> What's an MVP? A volunteer! Read the FAQ: http://mvp.support.microsoft.com/ Thanks, Dailya. The reason I tried a macro (which MIcrosoft Support recommended) was that I'd alrady tried Autotext. When I used this, it produced borders although the table I'd selected had none, and (if I remember correctly) it didn't have bold in one column as did the selected table. John > One approach, and the one usually recommended for repeating tables: > [quoted text clipped - 39 lines] > MacWord Tips: <http://word.mvps.org/Mac/WordMacHome.html> > What's an MVP? A volunteer! Read the FAQ: http://mvp.support.microsoft.com/ Hi John, I always use AutoCorrect instead of AutoText for these things (habit). I just tried it with a table that had no borders at all and with bold in just one cell. It reproduces fine. I don't know why AutoText isn't working for you but try AutoCorrect and see if it makes a difference. By the way, when you get rid of table borders, they turn gray; they don't actually disappear (except when you print). Could that be what you're seeing? Signature***Please always reply to the newsgroup!*** Beth Rosengard MacOffice MVP Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> My Site: <http://www.bethrosengard.com> On 10/8/06 8:18 AM, in article 1160320690.065921.236980@i3g2000cwc.googlegroups.com, "john@johnhands.com" > Thanks, Dailya. The reason I tried a macro (which MIcrosoft Support > recommended) was that I'd alrady tried Autotext. When I used this, it [quoted text clipped - 3 lines] > > John Hi Beth No. I wasn't seeing grey lines, but solid black ones that printed. But I'll try AutoCorrect instead. Many thanks John > Hi John, > [quoted text clipped - 28 lines] > > > > John Hi John: You do NOT want to do the macro! Here's why... (Yes, it works :-)) Sub Main() ' ' Insert or Format Table Macro ' Macro recorded 14/03/00 by John McGhie ' ' On Error GoTo Error Dim astyle As Style Dim aDoc As String Dim aTemplate As String Dim x As Integer Dim TabBodyText As Style Dim TabHeading As Style Dim TabBullet As Style Dim tabNumber As Style aTemplate = ActiveDocument.AttachedTemplate.FullName aDoc = ActiveDocument.FullName For Each astyle In ActiveDocument.Styles If UCase(astyle.NameLocal) = UCase("Table Body Text") Then Set TabBodyText = astyle If UCase(astyle.NameLocal) = UCase("Table Bullet") Then Set TabBullet = astyle If UCase(astyle.NameLocal) = UCase("Table Heading") Then Set TabHeading = astyle If UCase(astyle.NameLocal) = UCase("Table Number") Then Set tabNumber = astyle Next astyle If TabBodyText Is Nothing Then ActiveDocument.Styles.Add Name:="Table Body Text" Set TabBodyText = ActiveDocument.Styles("Table Body Text") With TabBodyText .AutomaticallyUpdate = False .BaseStyle = "Body Text" .NextParagraphStyle = "Table Body Text" End With With TabBodyText.Font .Name = BodyFont .Size = 10 .Bold = False .Italic = False End With With TabBodyText.ParagraphFormat .LeftIndent = 0 .RightIndent = 0 .SpaceBefore = 2 .SpaceBeforeAuto = False .SpaceAfter = 2 .SpaceAfterAuto = False .LineSpacingRule = wdLineSpaceSingle .Alignment = wdAlignParagraphLeft .WidowControl = False .KeepWithNext = False .KeepTogether = True .PageBreakBefore = False .FirstLineIndent = 0 .OutlineLevel = wdOutlineLevelBodyText End With End If If TabHeading Is Nothing Then ActiveDocument.Styles.Add Name:="Table Heading" Set TabHeading = ActiveDocument.Styles("Table Heading") With TabHeading .AutomaticallyUpdate = False .BaseStyle = "Table Body Text" .NextParagraphStyle = "Table Heading" End With With TabHeading.Font .Name = HeadingFont .Size = 10 .Bold = True .Italic = False End With With TabHeading.ParagraphFormat .LeftIndent = 0 .RightIndent = 0 .SpaceBefore = 2 .SpaceBeforeAuto = False .SpaceAfter = 2 .SpaceAfterAuto = False .LineSpacingRule = wdLineSpaceSingle .Alignment = wdAlignParagraphLeft .WidowControl = False .KeepWithNext = True .KeepTogether = True .PageBreakBefore = False .FirstLineIndent = 0 .OutlineLevel = wdOutlineLevelBodyText End With End If If TabBullet Is Nothing Then ActiveDocument.Styles.Add Name:="Table Bullet" Set TabBullet = ActiveDocument.Styles("Table Bullet") With TabBullet .AutomaticallyUpdate = False .BaseStyle = "Table Body Text" .NextParagraphStyle = "Table Bullet" End With With TabBullet.Font .Name = BodyFont .Size = 10 .Bold = False .Italic = False End With With TabBullet.ParagraphFormat .LeftIndent = 22 .RightIndent = 0 .SpaceBefore = 0 .SpaceBeforeAuto = False .SpaceAfter = 5 .SpaceAfterAuto = False .LineSpacingRule = wdLineSpaceSingle .Alignment = wdAlignParagraphLeft .WidowControl = True .KeepWithNext = False .KeepTogether = False .PageBreakBefore = False .FirstLineIndent = -17 .OutlineLevel = wdOutlineLevelBodyText End With TabBullet.ParagraphFormat.TabStops.ClearAll TabBullet.ParagraphFormat.TabStops.Add _ Position:=22, Alignment:=wdAlignTabLeft, Leader:= _ wdTabLeaderSpaces With ListGalleries(wdBulletGallery).ListTemplates(7).ListLevels(1) .NumberFormat = ChrW(61623) .TrailingCharacter = wdTrailingTab .NumberStyle = wdListNumberStyleBullet .NumberPosition = 6 .Alignment = wdListLevelAlignLeft .TextPosition = 22 .TabPosition = 22 .ResetOnHigher = 0 .StartAt = 1 .Font.Name = "Symbol" .LinkedStyle = "Table Bullet" End With End If If tabNumber Is Nothing Then ActiveDocument.Styles.Add Name:="Table Number" Set tabNumber = ActiveDocument.Styles("Table Number") With tabNumber .AutomaticallyUpdate = False .BaseStyle = "Table Bullet" .NextParagraphStyle = "Table Number" End With With tabNumber.Font .Name = BodyFont .Size = 10 .Bold = False .Italic = False End With With tabNumber.ParagraphFormat .LeftIndent = 22 .RightIndent = 0 .SpaceBefore = 0 .SpaceBeforeAuto = False .SpaceAfter = 2 .SpaceAfterAuto = False .LineSpacingRule = wdLineSpaceSingle .Alignment = wdAlignParagraphLeft .WidowControl = True .KeepWithNext = False .KeepTogether = False .PageBreakBefore = False .FirstLineIndent = -17 .OutlineLevel = wdOutlineLevelBodyText End With tabNumber.ParagraphFormat.TabStops.ClearAll tabNumber.ParagraphFormat.TabStops.Add _ Position:=22, Alignment:=wdAlignTabLeft, Leader:= _ wdTabLeaderSpaces With ListGalleries(wdNumberGallery).ListTemplates(7).ListLevels(1) .NumberFormat = "%1." .TrailingCharacter = wdTrailingTab .NumberStyle = wdListNumberStyleArabic .NumberPosition = 6 .Alignment = wdListLevelAlignLeft .TextPosition = 22 .TabPosition = 22 .ResetOnHigher = 0 .StartAt = 1 .LinkedStyle = "Table Number" End With End If If Not Selection.Information(wdWithInTable) Then ActiveDocument.Tables.Add Range:=Selection.Range, NumRows:=5, NumColumns:= _ 3, DefaultTableBehavior:=wdWord9TableBehavior, AutoFitBehavior:= _ wdAutoFitFixed End If Dim aTable As Table Set aTable = Selection.Tables(1) aTable.Select aTable.AutoFormat Format:=wdTableFormatGrid5, ApplyBorders:= _ True, ApplyShading:=True, ApplyFont:=False, ApplyColor:=False, _ ApplyHeadingRows:=True, ApplyLastRow:=False, ApplyFirstColumn:=False, _ ApplyLastColumn:=False, AutoFit:=True aTable.Select With Selection .Rows.AllowBreakAcrossPages = False .Paragraphs.Reset .Font.Reset .Style = ActiveDocument.Styles("Table Body Text") With .Borders(wdBorderLeft) .LineStyle = wdLineStyleSingle .LineWidth = wdLineWidth075pt .Color = wdColorAutomatic End With With .Borders(wdBorderRight) .LineStyle = wdLineStyleSingle .LineWidth = wdLineWidth075pt .Color = wdColorAutomatic End With With .Borders(wdBorderTop) .LineStyle = wdLineStyleSingle .LineWidth = wdLineWidth075pt .Color = wdColorAutomatic End With With .Borders(wdBorderBottom) .LineStyle = wdLineStyleSingle .LineWidth = wdLineWidth075pt .Color = wdColorAutomatic End With With .Borders(wdBorderHorizontal) .LineStyle = wdLineStyleSingle .LineWidth = wdLineWidth025pt .Color = wdColorAutomatic End With With .Borders(wdBorderVertical) .LineStyle = wdLineStyleSingle .LineWidth = wdLineWidth025pt .Color = wdColorAutomatic End With .Borders(wdBorderDiagonalDown).LineStyle = wdLineStyleNone .Borders(wdBorderDiagonalUp).LineStyle = wdLineStyleNone .Borders.Shadow = False End With With Options .DefaultBorderLineStyle = wdLineStyleSingle .DefaultBorderLineWidth = wdLineWidth025pt .DefaultBorderColor = wdColorAutomatic End With aTable.Rows(1).Select With Selection .Style = ActiveDocument.Styles("Table Heading") .Rows(1).HeadingFormat = True With .Shading .Texture = wdTexture10Percent .ForegroundPatternColor = wdColorAutomatic .BackgroundPatternColor = wdColorAutomatic End With End With aTable.AutoFitBehavior (wdAutoFitWindow) End Error: MsgBox "The Template has been damaged. See Tech Support.", vbCritical End Sub On 9/10/06 4:37 AM, in article 1160332667.937426.263970@h48g2000cwc.googlegroups.com, "john@johnhands.com" > Hi Beth > [quoted text clipped - 36 lines] >>> >>> John SignaturePlease reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to. John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410 Hi John Maybe I'm dumb, but I didn't understand what that progamming language meant or why the macro does not work. But if it doesn't work, then what is the best way to insert a specific table format that I use repeatedly? John > Hi John: > [quoted text clipped - 797 lines] > > --B_3243265427_15662445-- If you pasted directly from your browser into the Visual Basic Editor, it would convert the "spaces" into "non-breaking spaces". These are different characters: a non-breaking space is significant in VBA. To fix that, paste the code into SimpleText, save as Text Only, re-open it, and paste from there. Then, any line that turns red has been folded over. Delete the line-ender at the end of the first red line until it joins the line below it. That should fix it. Let me do that bit for you: There's a little attachment on this post. Save it to your hard drive. In the VBA Editor, go to the Insert menu, choose "File" and select this file. It will import into the Visual Basic Editor correctly for you. And no, you are not dumb: but that's a fairly advanced piece of code. Not recommended for your first venture into VBA :-) Now, do what Clive says: it's a LOT easier :-) Cheers On 9/10/06 11:43 PM, in article 1160401438.567270.98440@i42g2000cwa.googlegroups.com, "john@johnhands.com" > Hi John > [quoted text clipped - 880 lines] >> >> --B_3243265427_15662445-- SignaturePlease reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to. John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410 Hi John Maybe I'm dumb, but I didn't understand what that progamming language meant or why the macro does not work. But if it doesn't work, then what is the best way to insert a specific table format that I use repeatedly? John > Hi John: > [quoted text clipped - 797 lines] > > --B_3243265427_15662445-- On 9/10/06 11:48 PM, in article 1160401736.703976.302580@b28g2000cwb.googlegroups.com, "john@johnhands.com" <snip> > ... what is the best way to insert a specific > table format that I use repeatedly? > > John Hello John, One way, by AutoText, is described blow-by-blow under the heading 'Example creating and inserting a pre-formatted table via AutoText' on page 124 of some notes on the way I use Word for the Mac, titled "Bend Word to Your Will", which are available as a free download from the Word MVPs' website (http://word.mvps.org/Mac/Bend/BendWordToYourWill.html). [Note: "Bend Word to your will" is designed to be used electronically and most subjects are self-contained dictionary-style entries. If you decide to read more widely than the item I've referred to, it's important to read the front end of the document -- especially pages 3 and 5 -- so you can select some Word settings that will allow you to use the document effectively.] Cheers, Clive Huggan Canberra, Australia (My time zone is 5-11 hours different from the US and Europe, so my follow-on responses to those regions can be delayed) ============================================================ Avoid long delays before your post appears -- use Entourage or newsreader software -- see http://word.mvps.org/Mac/AccessNewsgroups.html ============================================================ Hi Beth I tried this and it worked while the document was open. But when I saved the document, quit Word, opened again, and tried the Autocorrect, it produced the table but with borders. This is what happened with Autotext. Once I save the document, somehow a defafult of a standard border for the table seems to override my specs. Since everyone says that a macro will corrupt, I really would appreciate learning what I should do. Many thanks John > Hi John, > [quoted text clipped - 28 lines] > > > > John Hi John: Go to Table>Insert>Table and insert a table to your satisfaction. Make sure you check the box that says "Set as default for new tables". Now hold down either Shift key and choose "Save All" to force a save of both the document and the template. That saves the specification for tables like the one you just produced. Now go to Tools>Templates and Add-ins and make sure "Automatically update styles on open" is NOT checked. If it is, it will update your table style each time you open the document, and if your default table style has borders, then borders you will have -- every time :-) If you save this as an Autocorrect, make sure you set "With" to "Formatted Text" otherwise it won't work properly. Cheers On 11/10/06 6:03 AM, in article 1160510606.557536.204030@h48g2000cwc.googlegroups.com, "john@johnhands.com" > Hi Beth > [quoted text clipped - 45 lines] >>> >>> John SignaturePlease reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to. John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410 Hi John I tried this. When I Saved All it asked me did I want to save changes to template, I said yes. But same result. With a new document AutoCorrect produced the table with all the properties EXCEPT it gave it a (what I assumed was the previous default) border. John > Hi John: > [quoted text clipped - 77 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 Hi John, Now I'm wondering if your Normal template is corrupt. But before testing it, go to AutoCorrect and AutoText and delete all your formatted table entries. Then, navigate to your Normal template (it's in Home/Documents/MicrosoftUserData). Quit out of Word and then rename Normal to anything else. When you relaunch Word, it will create a new default Normal. Now re-create your table again according to John McGhie's instructions, and remake your AutoText and/or Auto/Correct entry. Does the formatting stick now? If so, your old Normal template was corrupt. If you had heavily customized it, you can copy most of the customizations to the new Normal using the Organizer. More about all this here: <http://word.mvps.org/Mac/MacWordNormal.html> Good luck and keep us posted! Signature***Please always reply to the newsgroup!*** Beth Rosengard MacOffice MVP Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> My Site: <http://www.bethrosengard.com> On 10/11/06 10:37 AM, in article 1160588271.925401.211690@b28g2000cwb.googlegroups.com, "john@johnhands.com" > Hi John > [quoted text clipped - 86 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410 Hi John: Before saving your table as an AutoText, select the table and use Format>Style to Apply "Table Normal" style. I suspect you have a Table style applied and have not realised it. Table Styles were new in Word 2004. They are quite hard to get rid of once you have a table style stuck in use. 1) Basically, create a blank document, then insert a new table. 2) Use Table>Insert>Table.... 3) Make sure you choose AutoFormat and set it to (none) -- which is right at the top of the list. 4) Now select the entire table and choose Format>Style 5) Choose the "Table Normal" style and Apply Save THAT as your AutoText or AutoCorrect and the borders should go away and stay away. There's three sources of formatting for a table in Word: The Format>Borders and Shading dialog, the Table>...>AutoFormat dialog, and the Format>Style... Dialog. You have to set "None" in all three to kill the unwanted borders. Read the following Word help topics: "About borders and shading" "Add a border to a table or group of cells" "Change a border in a table" "What types of styles can you create and apply?" "Create a new table style" I think one problem you're having is that you are trying to avoid getting into the detail. But you're in a complex area: digging a little deeper will enable you to understand the tools involved a lot better. Cheers On 12/10/06 3:37 AM, in article 1160588271.925401.211690@b28g2000cwb.googlegroups.com, "john@johnhands.com" > Hi John > [quoted text clipped - 86 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410 SignaturePlease reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to. John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410 > "I think one problem you're having is that you are trying to avoid getting > into the detail" This would be supported by the OP apparently not bothering to look at the reference I gave to the article in which I describe a series of steps in detail to make customized tables an AutoText item. The only complexity, if it is that, is involved in the table example initially chosen, and I discuss the various pros and cons about the design alternatives to make the choice appropriate to one's requirements. Additionally, by including an adjacent paragraph mark the method avoids problems that particularly occur when copying and pasting because of a bug in the Table style introduced in Word 2004. And so on. Why don't I post it here? Because it is longer than the usual post and because I would be unable to include an actual example. Still, the next version of Word will cater to those who don't want to get into the detail. Maybe the OP should wait till then... :-\ Clive Huggan ============== On 12/10/06 8:54 PM, in article C1545C12.4E2B0%john@mcghie.name, "John McGhie [MVP - Word and Word Macintosh]" <john@mcghie.name> wrote: > Hi John: > [quoted text clipped - 131 lines] >>> Technical Writer. >>> Sydney, Australia +61 (0) 4 1209 1410 Clive Do I take it that I am "the OP"? I confess that I DID read your article several times, once with a colleague who is more technically experienced than me, and we both had difficulty following it. To a non-techie it isn't straightforward. For what it's worth we did try and follow John's steps and include an adjacent paragraph mark (which I managed to pick out of your article), but it still didn't work. Please don't assume we non-techies want everything on a plate. I have spent several hours trying to follow the various advices. Blame my stupidity, but not my lack of effort. John > > "I think one problem you're having is that you are trying to avoid getting > > into the detail" [quoted text clipped - 154 lines] > >>> Technical Writer. > >>> Sydney, Australia +61 (0) 4 1209 1410 Thanks for your response, John. That's useful to know. It's otherwise difficult to know whether to continue contributing if there is no response to a post, even an oblique one, from the original poster ( = "OP", which I used because there are two Johns in the thread). Here's a follow-on suggestion: remove the visibility of the horizontal lines (borders) in the sample table on page 124 of "Bend Word to Your Will" and select and copy the paragraph marks and the table, collectively. Paste that into a new blank document. Select again, then create an AutoText item. Does your problem persist? It *may* not, since you are creating the item from a contributed sample -- one which among several other characteristics does not contain Word 2004's default Table style that brings its own share of problems. If the problem does persist after that, then John McGhie's hypothesis that you have a corrupted document or Normal template is endorsed, or the problem applies to your particular configuration. The phenomenon you describe has certainly not been described before, and will be interesting to come to grips with. If you or your colleagues have time in due course -- and inclination -- to give me feedback on my article on tables as AutoText items, I'd be grateful. Most of those articles incorporate a lot of feedback from this NG -- which is a good thing, because after a while one loses the ability to see the shortcomings, or to describe with sufficient simplicity, as it is a constant challenge to describe simply the wonderful configurability (and foibles) of Word... Cheers, Clive Huggan ============ On 13/10/06 8:35 AM, in article 1160692501.334727.216280@k70g2000cwa.googlegroups.com, "john@johnhands.com" > Clive > [quoted text clipped - 177 lines] >>>>> Technical Writer. >>>>> Sydney, Australia +61 (0) 4 1209 1410 Thanks, Clive, and also Beth, John, Daiya, and the other professionals who freely give your time to helping us non-techies. Greatly appreciated. The reason that I don't respond immediately to every suggestion is that I have to earn a living as a writer, and that isn't a 9-5 job. So to read all the suggestions and the articles referrred to, and then (in this case) spend hours trying them out, has to be spread over several days. Two items of feedback: 1. Although I downloaded your electronic reference book, when I tried to print the other articles referred to, both Safari and Firefox would print only the first page. (I've given this feedback to the MVP webpage a couple of times in the past, with no response.). It's helpful for me to have a printout because I can read the articles when I'm not at my computer. 2. I suspect most non-techies like myself feel it's way over our heads, and sometimes confusing, to be told in detail the possible technical reasons why something hasn't worked. What we would most appreciate is a simple Step by Step (missing out no assumed steps) guide to a possible solution. This applies to your article. Again, thanks to all of you for your time. I'm still reading and will attempt solutions. John > Thanks for your response, John. That's useful to know. It's otherwise > difficult to know whether to continue contributing if there is no response [quoted text clipped - 213 lines] > >>>>> Technical Writer. > >>>>> Sydney, Australia +61 (0) 4 1209 1410 Hi John, Which other articles referred to? Beth On 10/13/06 1:54 PM, in article 1160772866.773216.65490@i3g2000cwc.googlegroups.com, "john@johnhands.com" > 1. Although I downloaded your electronic reference book, when I tried > to print the other articles referred to, both Safari and Firefox would > print only the first page. Hi Beth I think most of the articles on the word.mvps.org/FAQs site. Certainly the reference to how to use AutoText: http://word.mvps.org/FAQs/Customization/AutoText.htm John > Hi John, > [quoted text clipped - 8 lines] > > to print the other articles referred to, both Safari and Firefox would > > print only the first page. Hi John, I can't reproduce this. I just accessed the article you referenced below from Safari and printed it all of it (3 pages worth). I have to believe that there's something in your system (printer setup or driver, perhaps?) that's preventing these articles from printing out properly. Can you print long articles from other sites without any problem? Signature***Please always reply to the newsgroup!*** Beth Rosengard MacOffice MVP Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> My Site: <http://www.bethrosengard.com> On 10/13/06 2:35 PM, in article 1160775339.022660.272760@h48g2000cwc.googlegroups.com, "john@johnhands.com" > Hi Beth > [quoted text clipped - 16 lines] >>> to print the other articles referred to, both Safari and Firefox would >>> print only the first page. Hi Beth This is a mystery. I print out other long articles from other sites with no problem. But if I paste http://word.mvps.org/FAQs/Customization/AutoText.htm into Safari I get a blank screen. If I paste into Firefox I get the full article. But if I try and print I get only the first page. The Print Preview looks weird. I've done a window grab of the image and will try and attach it to this message. Thanks John Snapshot 2006-10-17 19-42-09.tiff PS: It only seems to want to paste the title and not the file. > Hi John, > [quoted text clipped - 36 lines] > >>> to print the other articles referred to, both Safari and Firefox would > >>> print only the first page. On 10/17/06 11:49 AM, in article 1161110967.221565.253250@i3g2000cwc.googlegroups.com, "john@johnhands.com" > This is a mystery. I print out other long articles from other sites > with no problem. [quoted text clipped - 4 lines] > > into Safari I get a blank screen. No mystery. Just refresh the page a few times in Safari. SignaturePaul Berkowitz MVP MacOffice Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html> AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/> Please "Reply To Newsgroup" to reply to this message. Emails will be ignored. PLEASE always state which version of Microsoft Office you are using - **2004**, X or 2001. It's often impossible to answer your questions otherwise. Paul Yes, this worked. But still a mystery to me at least, because this is the only site that I've had to reload several times from Safari before it appeared. And it only prints out one page from Firefox. I think I gave specs in earlier postings: MacWord 2004 v11.2, OSX 10.4.8 John > On 10/17/06 11:49 AM, in article > 1161110967.221565.253250@i3g2000cwc.googlegroups.com, "john@johnhands.com" [quoted text clipped - 22 lines] > **2004**, X or 2001. It's often impossible to answer your questions > otherwise. It's to do with the implementation of frames in Front Page, the Windows program used to make those web pages, and which are not compatible with Safari. They break some sort of standard protocol, but most browsers other than Safari know how to read them. I don't know the details because I'm not an HTML expert. The home Word MVP page, plus all the Mac Word pages, have been re-done to avoid this problem (and they look much nicer, too). Thank Beth Rosengard for that. Eventually all the Word MVP pages will be re-done. Whether that will happen first, or be beaten by Safari 3 in Leopard which is likely to be able to read the existing pages without refreshing, is anyone's guess. SignaturePaul Berkowitz MVP MacOffice Entourage FAQ Page: <http://www.entourage.mvps.org/faq/index.html> AppleScripts for Entourage: <http://macscripter.net/scriptbuilders/> Please "Reply To Newsgroup" to reply to this message. Emails will be ignored. PLEASE always state which version of Microsoft Office you are using - **2004**, X or 2001. It's often impossible to answer your questions otherwise. > From: "john@johnhands.com" <john@johnhands.com> > Organization: http://groups.google.com [quoted text clipped - 39 lines] >> **2004**, X or 2001. It's often impossible to answer your questions >> otherwise. Hi John: That's one of the "old" pages built using frames. Due to a bug, Safari will load only three frames per page: our "text" is in the fourth frame :-) As Paul says, if you refresh often enough, Safari will get it eventually. Of any other browser (including the very ancient Internet Explorer) will get it on the first try... Cheers On 18/10/06 7:00 AM, in article 1161118851.061192.135060@f16g2000cwb.googlegroups.com, "john@johnhands.com" > Paul > [quoted text clipped - 33 lines] >> **2004**, X or 2001. It's often impossible to answer your questions >> otherwise. SignaturePlease reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to. John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410 Hi John, Paul and John have explained the Safari issue so I won't go into that. But ... I can confirm the Firefox printing issue! As I told you before, Safari will print all three pages (and now that you know how to access the article in Safari, it should for you too). Yet Firefox will print only one page. I even changed the printing option from 'print all pages' to 'print pages 1 to 3' and it still printed just one page. My guess would be that this has something to do with how Firefox deals with frames (yes, another frames issue). The reason I think so is that Firefox prints the site footer at the bottom of that single page while Safari doesn't print the footer until the end of the article. IOW, the footer frame is fooling Firefox into thinking the article ends at the bottom of the visible window. Sorry about this, but I don't think there's anything we can do to fix this on our end (other than continue to convert the old frames site to the new CSS design). It's a bug in Firefox (that will probably never be fixed since layouts using frames are fading in favor of CSS layouts). Beth On 10/17/06 11:49 AM, in article 1161110967.221565.253250@i3g2000cwc.googlegroups.com, "john@johnhands.com" > Hi Beth > [quoted text clipped - 35 lines] >> Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> >> My Site: <http://www.bethrosengard.com> I've been working off and on with a website designer that does so for a living to help redesign our site (OssingingDesignGuild). And he says using frames is poor design to be avoided if possible. If you want to limit contents so that it only takes up so much space, you can do much better with tables instead and make the cell padding nothing. > Hi John, > [quoted text clipped - 63 lines] >>> Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> >>> My Site: <http://www.bethrosengard.com> Signature------------------------------------------------------------------------ Phillip M. Jones, CET |LIFE MEMBER: VPEA ETA-I, NESDA, ISCET, Sterling 616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868 Martinsville Va 24112 |pjones@kimbanet.com, ICQ11269732, AIM pjonescet ------------------------------------------------------------------------ If it's "fixed", don't "break it"! mailto:pjones@kimbanet.com <http://www.kimbanet.com/~pjones/default.htm> <http://www.kimbanet.com/~pjones/90th_Birthday/index.htm> <http://www.kimbanet.com/~pjones/Fulcher/default.html> <http://www.kimbanet.com/~pjones/Harris/default.htm> <http://www.kimbanet.com/~pjones/Jones/default.htm> <http://www.vpea.org> Yep. The frames were settled on by someone else, probably 10 years ago? Maybe only 6 or so? Back when frames were state of the art, anyhow. Beth redesigned the Mac portion of the site, but the rest of the site has thousands of pages, is maintained by one volunteer (John McGhie), and needs updated content for Word 2007 anyhow. Long process to redo it, and little help. Daiya > I've been working off and on with a website designer that does so for a > living to help redesign our site (OssingingDesignGuild). And he says [quoted text clipped - 69 lines] >>>> Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> >>>> My Site: <http://www.bethrosengard.com> SignatureDaiya Mitchell, MVP Mac/Word Word FAQ: http://www.word.mvps.org/ MacWord Tips: <http://word.mvps.org/Mac/WordMacHome.html> What's an MVP? A volunteer! Read the FAQ: http://mvp.support.microsoft.com/ Thanks Daiya: Yep: Frames are gone :-) Nearly 80 per cent of the site is now converted. The original poster just happened to pick three of the pages that are "not" yet converted :-) Given that we're just about to have to re-write most of them, I am not burning up my entire weekends and late nights on this :-) Cheers > Yep. The frames were settled on by someone else, probably 10 years ago? > Maybe only 6 or so? Back when frames were state of the art, anyhow. Beth [quoted text clipped - 79 lines] >>>>> Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> >>>>> My Site: <http://www.bethrosengard.com> SignaturePlease reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to. John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410 Many thanks to you all for the explanations and the hard work you're putting in. Because I had problems accessing the MVP pages with Safari (I didn't know that I had to reload several times), I used Firefox just to be able to see answers, although I couldn't print them all (apart from first page), and so I'm been using this site from Firefox. This hasn't help me to access the advice you've been giving on the Macro for Table Problems. But at least now I know how to from Safari. I've also been delayed from trying out your advice on the Table problem because my iMac stopped working properly, eventually Apple agreed to replace it, and the brand new replacement iMac wouldn't connect with the WWW. After much "diagnostics" with AppleCare, they concluded that the new iMac had hardware problems. They have just replaced it (albeit one with a German keyboard) and so I hope now, after so long, to try and implement your solutions. (Am I being overromantic in thinking that Apple standards were higher before Apple morphed into an iPod maker?) Thanks again John > Thanks Daiya: > [quoted text clipped - 101 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 Hello John, My heartfelt sympathies (and concurrence with your query at the end; either you are not being over-romantic or there are many other "over-romantics" around) ... Seeing you are doing a fair bit of posting here (and with interesting questions, I'd add), you would be better off using newsreader software or Entourage. Foremost among the advantages is that the posts appear in (almost) real time. Notes on the advantages, and how to configure Entourage for this purpose are at page 23 of "Bend Word to Your Will", available as a free download from the Word MVPs' website (http://word.mvps.org/Mac/Bend/BendWordToYourWill.html). Cheers, Clive Huggan ============= On 20/10/06 8:53 PM, in article 1161341582.315181.244290@i42g2000cwa.googlegroups.com, "john@johnhands.com" > Many thanks to you all for the explanations and the hard work you're > putting in. [quoted text clipped - 136 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410 Maybe we should chip together and buy him a case of Dom Perion(?) to get the others moved over. ;-) > Yep. The frames were settled on by someone else, probably 10 years ago? > Maybe only 6 or so? Back when frames were state of the art, anyhow. Beth [quoted text clipped - 78 lines] >>>>> Mac Word FAQ: <http://word.mvps.org/Mac/WordMacHome.html> >>>>> My Site: <http://www.bethrosengard.com> Signature------------------------------------------------------------------------ Phillip M. Jones, CET |LIFE MEMBER: VPEA ETA-I, NESDA, ISCET, Sterling 616 Liberty Street |Who's Who. PHONE:276-632-5045, FAX:276-632-0868 Martinsville Va 24112 |pjones@kimbanet.com, ICQ11269732, AIM pjonescet ------------------------------------------------------------------------ If it's "fixed", don't "break it"! mailto:pjones@kimbanet.com <http://www.kimbanet.com/~pjones/default.htm> <http://www.kimbanet.com/~pjones/90th_Birthday/index.htm> <http://www.kimbanet.com/~pjones/Fulcher/default.html> <http://www.kimbanet.com/~pjones/Harris/default.htm> <http://www.kimbanet.com/~pjones/Jones/default.htm> <http://www.vpea.org> Hi John: That's a good point you raise, and I believe we owe you an explanation of why we do things differently :-) One of the most cogent criticisms of the Microsoft Word help is that it does exactly what you ask. It tells users what to do; it never tells them why, or how the mechanism works. They do this on purpose, and research has proved time and again that this strategy best suits around 80 per cent of computer users. Like yourself, they just want to be told what to do. However, at word.mvps.org, our target audience is the "other" 20 per cent. These are users who either want or need the technical detail. If we set out to tell users WHAT to do for each problem, we will be correct around 80 per cent of the time. If the problem is exactly what we think it is, and the user's computer is exactly how they say it is, and the user does exactly what we tell them, the solution will work. However, in something more than 30 per cent of cases, one or more of the previous four conditions is not exactly true. Under those circumstances, the procedure won't work. And if that's all we have told the user, they're left with nowhere to go. You get a 30 per cent failure rate. Our articles intentionally provide as much detail as we have. No matter how minor or obscure, if it's at all likely to be relevant, we include it if we have it. Combined with the user's native ingenuity, this produces articles that are far more resilient in real-world usage. Our articles will cope with 95 to 98 per cent of the possible problems within their subject area. Yes, they're more complex. Yes, it takes longer. And Yes, our articles suit an enthusiast or professional audience. They're not so suitable for the new or amateur user. We do this quite intentionally. We see our site as picking up where he Microsoft Help and Microsoft Knowledgebase articles leave off, and trying to take the user the rest of the way. Microsoft is a public corporation: it has a duty to its shareholders not to waste money trying to serve the 20 per cent of users for whom standard articles are insufficient. We are a bunch of enthusiasts and hobbyists. Many of us are *also* professionals in this field. We write articles for people like us. We pride ourselves on giving you the answers that Microsoft can't or won't. Remember that many of the contributors of those articles are Microsoft MVPs. To become an MVP, it is necessary to know more about your chosen product than most of the people working for Microsoft do. Our articles tend to reflect this :-) HOWEVER: Your comments are very valuable, in that they remind us (once again) of the need for us to explain things properly when we're trying to help people who do not have either the interest or the inclination for in-depth technical work. I have already apologised to you privately for leaving you hanging in a tangle of technical detail. I'll do it again publicly! I should have recognised straight off the bat that you were a user who neither needed nor wanted the technical detail. I should have sent you a set of numbered steps. Worse: I knew that at the time! I'm sorry, I was tired and stressed after a heavy day of doing this stuff for a living, so my first answers to you were cryptic and inadequate to their audience. I told myself "I've done the right thing. I have sent him the missing piece of information. He has everything he needs if he assembles the pieces." But I was fooling myself. I didn't tell you how to fit the pieces together, and I did not tell you in which order to do it. So I left you hanging. For which, I apologise! Cheers On 14/10/06 6:54 AM, in article 1160772866.773216.65490@i3g2000cwc.googlegroups.com, "john@johnhands.com" > 2. I suspect most non-techies like myself feel it's way over our heads, > and sometimes confusing, to be told in detail the possible technical [quoted text clipped - 6 lines] > > John SignaturePlease reply to the newsgroup to maintain the thread. Please do not email me unless I ask you to. John McGhie <john@mcghie.name> Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant Technical Writer. Sydney, Australia +61 (0) 4 1209 1410 Hi John It's very generous of you, but there's no need to apologize. However, I do appreciate your explanation. I wonder, though, if there isn't a gap here. I only post a question on this site after I've exhaused the Word Help and Office Assistant and come up with no solution. And in one case after phoning up Microsoft Help at their exhorbitant rates. And I can confirm that you guys know FAR more than the Microsoft Help people. But I do feel over my head if too much technical detail is given, with assumptions that we non-techies know how to handle it. So my plea is for you to speak to us at our reasonably intelligent but non-expert level, rather than expert to expert. Since you've repeated your private apology, let me repeat my private thanks for the great help you've sent to me directly. Best wishes John > Hi John: > [quoted text clipped - 90 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 Hi everybody As you may have seen from post 31 on this topic, I've delayed in trying out your solutions to the table macro problem because of iMac hardware problems. I tried with the template that John kindly sent direct but, I'm afraid, with no success. I did read all the Help topics you suggested and studiously set all means of styling table borders to None (although I never used Word's own table styles because they didn't fit what I wanted.) John's template resembled the one I had created, but I used his. This is what happened. 1. When I copied and pasted into a blank document, it appeared as it should. 2. When I copied and pasted into my book ms document, it appeared with borders. 3. Using my book ms doc, I created a new Table Normal style based on John's table and again set borders to None. It didn't make any difference. 4. I selected John's table for an AutoCorrect entry, replacing ddddd with John's table as Formatted Text and clicked Add. 5. When I went to my book ms and typed ddddd nothing happened, even when I tabbed. 6. When I went to a blank document and typed ddddd nothing happened. When I tabbed, the table appeared with borders. 7. I went back to the AutoCorrect list and found that next to ddddd was John's table, BUT with borders (which weren't there when I added it to the AutoCorrect list). This is what I had found before I first posted this problem. So there seems at least two problems here: (a) AutoCorrect is not even kicking in with my book document and needs a tab button to kick in after typing the first 5 letters (Word Help says it should automatically correct after 4) in a blank document; (b) Using John's template and switching to None all three means of adding borders to tables, it is still adding borders. Call me dumb, but I don't know the solution. John > Hi John: > [quoted text clipped - 139 lines] > Technical Writer. > Sydney, Australia +61 (0) 4 1209 1410 Hello John, If it were not that your problem has so far been so intractable, I would not bother to post this -- I'm not at all confident that it will fix things. But here goes... Did you get the same results when trying my suggestion of 13 October?: > "Here's a follow-on suggestion: remove the visibility of the horizontal lines > (borders) in the sample table on page 124 of "Bend Word to Your Will" and [quoted text clipped - 4 lines] > contain Word 2004's default Table style that brings its own share of > problems." Background: soon after Word 2004 was issued (or maybe it was an update -- can't remember) I experienced a bizarre set of problems when copying the tables referred to above -- but not always. In Word 2001 there had been no problem. I am fairly certain that one version of the problems (there were several) involved borders I had set to invisible becoming visible. I also noted at the time that Word had changed some of my styles to Table Normal (or Table Grid??? -- didn't record what it was; I was in a hurry and hopping mad that someone had fiddled with Word's established table mechanism, adding a "Word is here to help you" feature that hadn't been properly thought through -- i.e., as with a great many of the problems we suffer in Word). I went no further into it because (a) I discovered that this new impediment could be avoided by copying over the the paragraph mark that precedes (i.e., is immediately above, and external to) the table when you select the table for copying, and (b) the aberrant behaviour was so varied. (I also use AutoText for this purpose, not AutoCorrect, but that should not make any difference.) Please note that some MVPs have told me they do not think it is necessary to do what I describe on page 124 of "Bend Word to Your Will" -- especially in confining oneself to tailor-made styles and selecting the preceding paragraph mark -- because they have not had problems. But the problems I've experienced are not consistently reproducible and I doubt that other MVPs copy tables as often as I do (I do that often in my professional work because I deal extensively with contributed, or collaboratively developed, documents). I mention this not out of discourtesy to others but to make clear that by following the instructions in Word's Help, and probably John's example, you will be eligible to reproduce the problems I have experienced, albeit that they *may* not be applicable to your underlying problem -- the above may be a wild goose chase and may therefore only be useful to unequivocally eliminate a potential factor. But one never knows... Cheers, Clive Huggan ============= On 22/10/06 8:40 PM, in article 1161513604.940096.102260@i42g2000cwa.googlegroups.com, "john@johnhands.com" > Hi everybody > [quoted text clipped - 200 lines] >> Technical Writer. >> Sydney, Australia +61 (0) 4 1209 1410 Hi Clive Forgive the delay in response. I've been having some problems with the Intel dual processor iMac that Apple replaced their replacement with. Yes, I did try your suggestion. But: 1. Word wouldn't let me remove the borders from your sample table in BWYW 2. After I copied it to a blank document, including both preceding and succeeding para marks, it still wouldn't let me remove the borders. Hence it was even obdurate than John's template, which at least copied to the same document and retained the No Borders. John > Hello John, > [quoted text clipped - 256 lines] > >> Technical Writer. > >> Sydney, Australia +61 (0) 4 1209 1410 Hello John, Just for my education: when you say "Word wouldn't let me remove the borders from your sample table", what did you observe when you went to Format menu -> Borders and Shading -> Borders? Greyed-out border buttons in the right-hand ("Preview") pane? And what did it look like when you printed it? (I'm aware that you said in another context "I wasn't seeing grey lines, but solid black ones that printed".) I have reviewed all the posts in this thread and I believe all angles in the problem area have been covered. I only have two other ideas. The first would be whether your problem is caused (or related to) the presence of a haxie somewhere. For example, I found that some bizarre things occurred in Word when I installed iClip. The second is to contact a local Apple retailer that has an employee who knows Word well and who could review your actions while sitting next to you. The fee could be worth it. (I know you mentioned your colleague; I'm thinking of someone who has more extensive day-to-day experience.) Alternatively, you might find an expert in a local Mac user group. From my experience (including an example only this week in my own user group), sitting side-by-side will sometimes reveal things being done that are not reported in posts on a newsgroup because they appear fundamental to the poster (but in reality can be highly significant). You should print out the relevant posts in this thread to show this person. I am led to make the latter suggestion because no-one else is reporting your problem. However, I hasten to add that Intel-powered Macs are new and some problems have brought us into hitherto uncharted waters. I'm making that suggestion because my next move, if I were in your situation, could well be to consider buying a second-hand PowerPC (pre-Intel) Mac. Now, I know that's extreme, and it would depend on how important the "lost" capability is in your work. However, subject to the two suggestions I make above, I can't think of anything else. I certainly feel for you... :-\ Cheers, Clive Huggan ============ On 26/10/06 9:18 PM, in article 1161861505.874137.64900@m7g2000cwm.googlegroups.com, "john@johnhands.com" > Hi Clive > [quoted text clipped - 283 lines] >>>> Technical Writer. >>>> Sydney, Australia +61 (0) 4 1209 1410 Hi Clive This just gets odder. When I tried before to follow your suggestion, I highlighted your table on p.124, changed borders to No borders (nothing happened with your table) put line weight at zero (nothing happened with your table), and then put Type of Border at No border (again nothing happened with your table). I've just tried it again. When I changed borders to No Borders, again nothing happened, but this time when I put Type of Border at No Border the lines DID disappear from your border. So I copied it, plus preceding and succeeding para marks to a new document, and selected it as AutoCorrect (I think Beth is right, and it's quicker to work with that AutoText), and IT WORKED! Which is really strange because even when AutoCorrect was throwing up a version with borders it needed several tabs to get it to operate. So I guess I should now try to see if it works when I alter your table to the specs I want (2 columns, first bold, specific col widths etc). Someone more technically adept than me at University College London came up with a macro solution. She didn't write it all in Visual Basic, but recorded a macro (which produced a table with borders in spite of the specs of no borders), recorded another macro that simply removed all borders, produced the results of both in Basic, and then cut and pasted parts of the second macro into the first. The combined Visual Basic macro produces the table to the specs I need. I remember that many of you guys thought that a macro wasn't a good idea, but for what it's worth, the following works, whereas my previous attempts at recording a macro hadn't. Do you still think its' a bad idea to use a macro? Is it better to try and adapt Clive's table as an AutoCorrect? John ActiveDocument.Tables.Add Range:=Selection.Range, NumRows:=1, NumColumns:= _ 2, DefaultTableBehavior:=wdWord9TableBehavior, AutoFitBehavior:= _ wdAutoFitFixed Selection.Tables(1).Select Selection.Tables(1).Rows.LeftIndent = CentimetersToPoints(1.44) Selection.Tables(1).PreferredWidthType = wdPreferredWidthPoints Selection.Tables(1).PreferredWidth = CentimetersToPoints(12.69) With Selection.Tables(1) .Borders(wdBorderLeft).LineStyle = wdLineStyleNone .Borders(wdBorderRight).LineStyle = wdLineStyleNone .Borders(wdBorderTop).LineStyle = wdLineStyleNone .Borders(wdBorderBottom).LineStyle = wdLineStyleNone .Borders(wdBorderVertical).LineStyle = wdLineStyleNone .Borders(wdBorderDiagonalDown).LineStyle = wdLineStyleNone .Borders(wdBorderDiagonalUp).LineStyle = wdLineStyleNone .Borders.Shadow = False End With With Options .DefaultBorderLineStyle = wdLineStyleSingle .DefaultBorderLineWidth = wdLineWidth050pt .DefaultBorderColor = wdColorAutomatic End With Selection.Rows.AllowBreakAcrossPages = False Selection.MoveLeft Unit:=wdCharacter, Count:=1 Selection.Tables(1).Columns(1).PreferredWidthType = wdPreferredWidthPoints Selection.Tables(1).Columns(1).PreferredWidth = CentimetersToPoints(2.85) Selection.Font.bold = wdToggle Selection.MoveRight Unit:=wdCell Selection.Tables(1).Columns(2).PreferredWidthType = wdPreferredWidthPoints Selection.Tables(1).Columns(2).PreferredWidth = CentimetersToPoints(9.84) Selection.Tables(1).Select With Selection.Cells(1) .WordWrap = True .FitText = False End With Selection.MoveLeft Unit:=wdCharacter, Count:=1 > Hello John, > [quoted text clipped - 329 lines] > >>>> Technical Writer. > >>>> Sydney, Australia +61 (0) 4 1209 1410 Clive I've tried to adapt the copy of your table, but I can't figure out how to turn it into two columns rather than one. John > Hi Clive > [quoted text clipped - 414 lines] > > >>>> Technical Writer. > > >>>> Sydney, Australia +61 (0) 4 1209 1410 Clive I've tried to adapt the copy of your table, but I can't figure out how to turn it into two columns rather than one. John > Hi Clive > [quoted text clipped - 414 lines] > > >>>> Technical Writer. > > >>>> Sydney, Australia +61 (0) 4 1209 1410 Thanks for asking this question, John -- I have now added the answer to "Bend Word to Your Will". Table menu -> Insert -> Table -> Number of columns [insert a number]. Then specify AutoFit behaviour as: Initial column width Auto (don¹t use "AutoFit to contents"). Then configure via Format menu -> Borders and shading -> Borders (do not use the "Split cells" feature on the Table menu). Those two "don'ts" are, um, to minimize potential corruption. ;-) Cheers, Clive ======= On 28/10/06 7:44 AM, in article 1161981428.362541.269860@m7g2000cwm.googlegroups.com, "john@johnhands.com" > Clive > [quoted text clipped - 461 lines] >>>>>>> Technical Writer. >>>>>>> Sydney, Australia +61 (0) 4 1209 1410 Thanks, Clive I know how to create a 2-column table, but, despite having specified No Borders, it produced lines in AutoText and AutoCorrect. What I was trying to do was to take *your* template (which, I think you said, you'd created in a version before Word 2004 and therefore didn't have 2004's problems for tables) and turn that into 2 columns. But if you think that a macro won't corrupt, I guess I'll go with the one my colleague produced. Once again, many thanks to all of you MVPs who've spent so much time trying to solve this problem. John PS: If this reply appears twice, it's because my first attempt produced an error messge saying that unable to display, please try again. > Thanks for asking this question, John -- I have now added the answer to > "Bend Word to Your Will". [quoted text clipped - 481 lines] > >>>>>>> Technical Writer. > >>>>>>> Sydney, Australia +61 (0) 4 1209 1410 Enjoy your success-of-a-sort, John! Meantime, we will scratch our heads. There is something inherently unusual in your configuration, because all a macro does is trigger the mechanisms that are triggered in the normal course of events via menus, toolbar buttons or keyboard shortcuts. But you have a workaround. And we'll wait to get more information if/when someone else has the same problem. Cheers, Clive Huggan Canberra, Australia (My time zone is 5-11 hours different from the US and Europe, so my follow-on responses to those regions can be delayed) ============================================================ On 29/10/06 7:31 AM, in article 1162067511.993770.58470@e64g2000cwd.googlegroups.com, "john@johnhands.com" > Thanks, Clive > [quoted text clipped - 531 lines] >>>>>>>>> Technical Writer. >>>>>>>>> Sydney, Australia +61 (0) 4 1209 1410 Great news, John! If a macro works for you, go for it! There's nothing inherently "weak" about doing something in Word via a macro, since all a macro does is trigger Word's inherent mechanisms (as distinct from triggering them via menus, toolbar buttons or keyboard shortcuts). Likewise, it matters not one whit whether you use AutoCorrect or AutoText, which are essentially the same mechanism, triggered differently. I personally find it easier to use AutoText to initiate the large variety of pre-designed tables I have (it's easy to type in the codes -- for example, "4ch" for 4 columns, horizontal lines only -- in an otherwise blank paragraph and keying Command-Option-v, without needing to select the letters) but I could probably use the same codes in AutoCorrect (except that they may be needed as text in some of my work). But otherwise I nearly always use AutoCorrect (which I made use of, incidentally, about 10 times in typing this post). This all reflects that once one gains a good understanding of Word, there are almost invariably between two and five ways of doing anything. Vexatious it may be out of the box, but Word is a wonderfully configurable application, non? Cheers, Clive ======= On 28/10/06 6:24 AM, in article 1161980662.184311.222690@m7g2000cwm.googlegroups.com, "john@johnhands.com" > Hi Clive > [quoted text clipped - 438 lines] >>>>>> Technical Writer. >>>>>> Sydney, Australia +61 (0) 4 1209 1410 |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.