| Home |
| Search |
| Today's Posts |
|
#1
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
Fill-In removes toolbars
Hi all. I have a Word 2003 mail merge document that has a FILLIN
field in it. The FILLIN works fine but the output document has no menu or toolbars at all. This means I can't print, save, format, etc. If I take out the FILLIN I get them. Any help? Rgds, Jaime |
|
#2
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
|
Fill-In removes toolbars
If these merges are being run by automating Word, I've read that you may
need to issue .Activate on the Window (and possibly set .Visible to True - the ssequence may be significant). Otherwise, no clues, sorry. Peter Jamieson wrote in message oups.com... Hi all. I have a Word 2003 mail merge document that has a FILLIN field in it. The FILLIN works fine but the output document has no menu or toolbars at all. This means I can't print, save, format, etc. If I take out the FILLIN I get them. Any help? Rgds, Jaime |
|
#3
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
|
Fill-In removes toolbars
Hi Peter,
We have a program our customers use which automates Word to perform mail merges and over time two problems surfaced; one was that sometimes after the merge the menu bar and toolbars would be missing, and the other was that sometimes the menu bar and toolbars would be there but would be inactive until Word's window state was changed (e.g. by minimising and maximising Word). The problem of the missing toolbars seemed to happen if Word "thought" the merge had been interrupted - possibly by some types of error, or by fill-in fields. In our code we set the .Visible property of the application object to true before starting the merge to get around that. We used the .Activate method of the application object to get around the problem of the inactive toolbars. I didn't write the code but I've just read through it and the order that we used is: Set the app visible. Activate the app. Perform the merge (and maybe do other stuff). Activate the app. Not sure if both activations are necessary or whether this was "belt and braces". Regards. Ed "Peter Jamieson" wrote: If these merges are being run by automating Word, I've read that you may need to issue .Activate on the Window (and possibly set .Visible to True - the ssequence may be significant). Otherwise, no clues, sorry. Peter Jamieson wrote in message oups.com... Hi all. I have a Word 2003 mail merge document that has a FILLIN field in it. The FILLIN works fine but the output document has no menu or toolbars at all. This means I can't print, save, format, etc. If I take out the FILLIN I get them. Any help? Rgds, Jaime |
|
#4
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
|
Fill-In removes toolbars
Hello again,
I should have been a bit clearer about when the menu bar and toolbars would go missing. This would only happen with an "interruption" to the merge when Word was not yet visible. If Word was already visible we would not get the problem. Cheers. Ed "Peter Jamieson" wrote: If these merges are being run by automating Word, I've read that you may need to issue .Activate on the Window (and possibly set .Visible to True - the ssequence may be significant). Otherwise, no clues, sorry. Peter Jamieson wrote in message oups.com... Hi all. I have a Word 2003 mail merge document that has a FILLIN field in it. The FILLIN works fine but the output document has no menu or toolbars at all. This means I can't print, save, format, etc. If I take out the FILLIN I get them. Any help? Rgds, Jaime |
|
#5
Posted to microsoft.public.word.mailmerge.fields
|
|||
|
|||
|
Fill-In removes toolbars
Hi Ed,
Thanks, Peter Jamieson "Ed" wrote in message ... Hi Peter, We have a program our customers use which automates Word to perform mail merges and over time two problems surfaced; one was that sometimes after the merge the menu bar and toolbars would be missing, and the other was that sometimes the menu bar and toolbars would be there but would be inactive until Word's window state was changed (e.g. by minimising and maximising Word). The problem of the missing toolbars seemed to happen if Word "thought" the merge had been interrupted - possibly by some types of error, or by fill-in fields. In our code we set the .Visible property of the application object to true before starting the merge to get around that. We used the .Activate method of the application object to get around the problem of the inactive toolbars. I didn't write the code but I've just read through it and the order that we used is: Set the app visible. Activate the app. Perform the merge (and maybe do other stuff). Activate the app. Not sure if both activations are necessary or whether this was "belt and braces". Regards. Ed "Peter Jamieson" wrote: If these merges are being run by automating Word, I've read that you may need to issue .Activate on the Window (and possibly set .Visible to True - the ssequence may be significant). Otherwise, no clues, sorry. Peter Jamieson wrote in message oups.com... Hi all. I have a Word 2003 mail merge document that has a FILLIN field in it. The FILLIN works fine but the output document has no menu or toolbars at all. This means I can't print, save, format, etc. If I take out the FILLIN I get them. Any help? Rgds, Jaime |
| Reply |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| Pasting removes header | Microsoft Word Help | |||
| Why do I lose the toolbars when I use fill-in fields? | Mailmerge | |||
| Format, autoformat removes paragraph markers | Microsoft Word Help | |||
| Remove hidden data removes style modification | Microsoft Word Help | |||
| acrobat comments toolbars fill half the screen in word 2003 | Microsoft Word Help | |||
Linear Mode
