Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Mailmerge and Fax / May 2007

Tip: Looking for answers? Try searching our database.

Fill-In removes toolbars

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jcook@y-prime.com - 12 May 2007 06:21 GMT
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
Peter Jamieson - 12 May 2007 07:30 GMT
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

> 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
[quoted text clipped - 5 lines]
> Rgds,
> Jaime
Ed - 13 May 2007 19:21 GMT
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

> 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 -
[quoted text clipped - 13 lines]
> > Rgds,
> > Jaime
Peter Jamieson - 14 May 2007 09:29 GMT
Hi Ed,

Thanks,

Peter Jamieson
> Hi Peter,
>
[quoted text clipped - 50 lines]
>> > Rgds,
>> > Jaime
Ed - 13 May 2007 20:00 GMT
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

> 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 -
[quoted text clipped - 13 lines]
> > Rgds,
> > Jaime
 
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.