mail merge with fillin field - menus and toolbars disappear

[Daryl]

I have an automated mail merge process which works fine
until a document with a fillin field is merged. The
merge works OK but the Word Application has no menus or
toolbars. It looks like some kind of preview window. I
can edit the document but not print, etc. since there is
no way to select options and/or function.

 

[Cindy Meister -WordMVP-]

Hi Daryl,

Please show us the relevant part of the code (starting or
access the Word application, onwards).

Generally, I'd say this means your program hasn't used the
.Activate method on the Word window (and it makes a
difference whether you use it before or after making it
.Visible)

I have an automated mail merge process which works fine
until a document with a fillin field is merged. The
merge works OK but the Word Application has no menus or
toolbars. It looks like some kind of preview window. I
can edit the document but not print, etc. since there is
no way to select options and/or function.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update
Jan 24 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any
follow question or reply in the newsgroup and not by e-mail

 

[Daryl]

Thanks, that fixed it. The reason I put the .visible =
False there in the first place was to remove the
flickering during the merge. I guess I will live with
the flickering.

When you mentioned the order of the .activate
and .visible, can you tell me more about how the order
affects the process?

 

[Cindy Meister -WordMVP-]

Hi Daryl,

The problem was (of course) that the FILLIN field was
forcing the .Visible, but the application hadn't been
activated. You might try putting an .Activate in their and
NOT the .Visible. Then it may only become visible if a
FILLIN field or other message forces it?

I can never keep straight which has to come first, but I
think it's the Activate. If you have it the other way
around, you (sometimes) get the same thing you were seeing
with the FILLIN fields.

Thanks, that fixed it. The reason I put the .visible =
False there in the first place was to remove the
flickering during the merge. I guess I will live with
the flickering.

When you mentioned the order of the .activate
and .visible, can you tell me more about how the order
affects the process?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update
Jan 24 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any
follow question or reply in the newsgroup and not by e-mail