Word Macro Template Problem - freezing rich text fields?

[sean]

Hi all,

I'm hoping you can help. I created a Word Form as a Word Macro-Enable
Template (.dotm) in Word 2007. Now I've used a mixture of things: ric
text fields inside multiple tables, grouped radio buttons, 2 x dat
pickers inside a table, and 3 x check boxes.

I have then Protected and Restricted Editing to 'Filling in Forms' a
suggested in Word Help. I've then Started Enforcing Protection an
entered a password before saving.

When I open the template as a new document everything looks OK. When
start enetring text into the rich text fields it works fine...to
point. Usually, but not always, the text fields after the radio butto
groups don't seem to work (they just refuse to accept the text that yo
enter). The rich text field can be sellected with the mouse but n
cursor flashes and text cannot be entered. The point at which thi
happens is not consistent. After an inconsistent amount of time (a fe
minutes of clicking on different boxes) it seems to correct itself an
allow the remaining the rich text fields to have text entered.

I have tried a number of things that haven't solved the problem
including:
1. Word Options> Trust Centre> Trust Centre Settings> turned on 'Trus
Access to the VBA project object model' and turned on 'Enable al
macros'.
2. Added the folder in which the template resides to the 'Truste
Locations' list.
3. Running McAfee Total Protection Service but no pop-ups have come u
notifying of any issue.
4. Tried opening the template as a new document on 4 seperate machine
and same problem comes up in each.

(copy of the file is attached .dotm - unprotected)

I can't work out what the problem is? Can anyone offer any ideas? Ha
anyone come across a problem like this before?

Any help would be greatly appreciated.

Thanks,

Sea

+-------------------------------------------------------------------
|Filename: FM Plan Quote Request v04.zip
|Download: http://www.thecodecage.com/forumz/attachment.php?attachmentid=203
+-------------------------------------------------------------------

 

[Cindy M.]

Hi Sean,

I've never seen anything like you describe, and it's difficult to even
begin to guess what may be happening as you don't go into any detail
about what type of fields all of these are. I'm guessing the Rich Text
and datepickers are content controls? Do the "radio buttons" come from
the Legacy tools? Exactly how have they been "grouped"? You mention a
table: are the fields that cause the problem within the same table? In
what relation to each other? Are you using the mouse or the keyboard to
navigate the form? Do you see the same issues if you do NOT protect the
document as a form?

I'm hoping you can help. I created a Word Form as a Word Macro-Enabled
Template (.dotm) in Word 2007. Now I've used a mixture of things: rich
text fields inside multiple tables, grouped radio buttons, 2 x date
pickers inside a table, and 3 x check boxes.

I have then Protected and Restricted Editing to 'Filling in Forms' as
suggested in Word Help. I've then Started Enforcing Protection and
entered a password before saving.

When I open the template as a new document everything looks OK. When I
start enetring text into the rich text fields it works fine...to a
point. Usually, but not always, the text fields after the radio button
groups don't seem to work (they just refuse to accept the text that you
enter). The rich text field can be sellected with the mouse but no
cursor flashes and text cannot be entered. The point at which this
happens is not consistent. After an inconsistent amount of time (a few
minutes of clicking on different boxes) it seems to correct itself and
allow the remaining the rich text fields to have text entered.

I have tried a number of things that haven't solved the problem,
including:
1. Word Options> Trust Centre> Trust Centre Settings> turned on 'Trust
Access to the VBA project object model' and turned on 'Enable all
macros'.
2. Added the folder in which the template resides to the 'Trusted
Locations' list.
3. Running McAfee Total Protection Service but no pop-ups have come up
notifying of any issue.
4. Tried opening the template as a new document on 4 seperate machines
and same problem comes up in each.

(copy of the file is attached .dotm - unprotected)

I can't work out what the problem is? Can anyone offer any ideas? Has
anyone come across a problem like this before?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

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

 

[sean]

Hi Cindy

Thanks for your reply. I thought I'd attach a copy of the macro
template (dotm) in a zip file and attach it to the post to make it
easier for someone work out what I may have done wrong or if it's a MS
issue.

You are welcome to download and take a closer look. I'm sure this will
give you more information than I could offer in writing. The template is
unprotected so you can protect it yourself before opening as a new
document form.

Your question about using mouse or keyboard to navigate; I tried using
both and still had the same problem.

At first I thought it maybe the virus scanner (we use McAfee TPS
4.7.0.752 Patch 4) interfering with macro but there's been no pop-ups or
anything in the logs.

If you can offer any help or suggestions it would be appreciated.

Thanks,
Sean

Hi Sean,

I've never seen anything like you describe, and it's difficult to even
begin to guess what may be happening as you don't go into any detail
about what type of fields all of these are. I'm guessing the Rich Text
and datepickers are content controls? Do the "radio buttons" come from
the Legacy tools? Exactly how have they been "grouped"? You mention a
table: are the fields that cause the problem within the same table? In
what relation to each other? Are you using the mouse or the keyboard
to
navigate the form? Do you see the same issues if you do NOT protect
the
document as a form?

 

[sean]

I just logged the problem with Microsoft and received the followin
reply:

"I have reproduced the issue on my side based on your steps. I
addition, I created some new .docm files, and add Rich Text control an
Check box ActiveX control. I also can reproduce the issue. Sorry for th
inconvenience that you have experienced.

Within my responsibility, I will report the issue to our product team
They will investigate on the issue. However, we cannot guarantee th
exact time that the issue will be fixed. Thank you for your kin
understanding.

In the future, you can report product problem and submit produc
suggestions directly through the following channel.

Report a Microsoft Product Bug:
If you think you have found a bug in a Microsoft product, pleas
contact our Microsoft Product Support Services department. (800
MICROSOFT (642-7676)

Submitting suggestions for product enhancement:

Legitimate Wishes fit into the following guidelines. Please submit to
http://tinyurl.com/maop93

• Enhancement or feature addition to existing Microsoft products
• Reproducible problem or bug with current version that need
resolution
• Cannot find documentation of feature within the help files
• Difficulty using the product
• All beta products
• Product packaging complaints
• Added accessibility feature for a Microsoft product

So, the problem is now 'recognised' by Microsoft and has been logged t
be looked at by the 'product team'.

At least I know I'm not crazy and it is an issue with MS Word.

Thanks for you help Cindy. I guess I will have to redesign the for
taking out one control type at a time until I find whats causing th
conflict.

Thanks,

Sea

 

[chelleade]

Hi Sean,

I have the same problem with the rich text content controls and
protecting the document. All the other active X items work fine but the
rich text content controls go crazy when I try and protect the document.
I have tried contacting microsoft but here in NZ the customer service
centre has to be staffed with the most unhelpful people that I have ever
come across.

Therefore is there any chance that you could share the solution that
microsoft sent to you - if in fact they have come up with a solution
(which I am doubting based on the service that I have received to
date).

Chelle