Active X controls changing names

[Charlie]

I have been having this issue randomly for the last year with a set of Word
status reports that we created. With no pattern, the controls will just
rename themselves to default control names (like commandbutton1). This
causes all of the VBA code behind the document to stop working obviously.
What's even weirder is that the control no longer behave normally, but behave
as if they were in design mode. I saw a while back on this newsgroup that it
was recommended to change the names of the controls from the default given.
However, all of the controls on my documents already have custom names.
There are quite a few controls on the document (20+), and up until now we
have just considered this a bug with Word. Hopefully someone out there can
give me some advice though. Thank you in advance!

 

[Jean-Guy Marcil]

Charlie was telling us:
Charlie nous racontait que :

I have been having this issue randomly for the last year with a set
of Word status reports that we created. With no pattern, the
controls will just rename themselves to default control names (like
commandbutton1). This causes all of the VBA code behind the document
to stop working obviously. What's even weirder is that the control no
longer behave normally, but behave as if they were in design mode. I
saw a while back on this newsgroup that it was recommended to change
the names of the controls from the default given. However, all of the
controls on my documents already have custom names. There are quite a
few controls on the document (20+), and up until now we have just
considered this a bug with Word. Hopefully someone out there can
give me some advice though. Thank you in advance!

I am afraid I do not have a solution for you,.

This question comes up regularly in the NG, and I do not remember seeing a
definite answer.

This is why most experience Word Template producer do not use ActiveX
control (Another strike against them is security in later Word version, for
many users, with their security set to high, Word goes into Design mode. Yet
another is that ActiveX can cause problems when documents are opened in
different Word versions.)

And this is not an Office thing, this is specific to Word. In Excel they are
well behaved, at least, this is what I have been told.

--
Salut!
_______________________________________
Jean-Guy Marcil - Word MVP
(e-mail address removed)
Word MVP site: http://www.word.mvps.org

 

[Charlie Evans]

Well, it is a little reassuring that the problem is not just specific to me.
However it sure it is frustrating. I'm not sure if we can maintain all of
the functionality in our status reports without using the ActiveX controls.
Would you recommend just using standard form elements instead? That may be
hard for me to convert to.

Charlie

 

[Jean-Guy Marcil]

Charlie Evans was telling us:
Charlie Evans nous racontait que :

Well, it is a little reassuring that the problem is not just specific
to me. However it sure it is frustrating. I'm not sure if we can
maintain all of the functionality in our status reports without using
the ActiveX controls. Would you recommend just using standard form
elements instead? That may be hard for me to convert to.

You could use a MacroButton field behind an inline JPG of command button.
But you would not get a "press down" effect.

What other ActiveX controls are you using?

I usually use a combination of toolbar buttons and userforms.

--
Salut!
_______________________________________
Jean-Guy Marcil - Word MVP
(e-mail address removed)
Word MVP site: http://www.word.mvps.org