Storing a command button in the Quick Parts

[Alexander]

Hello,

There is a problem that I cannot get a work-around. I am trying to design a
template document (.dotm). It has a drop down list content control with
several options. A simple macro code changes a predesigned form in the
document body, depending on a chosen option from the drop down list. All the
predesigned forms are stored as quick parts in that template document. One of
the forms has a command button in it. So, when a user chooses a form he wants
to fill, a policy statement appears in the body. User can accept the policy
by pressing the command button and a form will appear after that.
Everything works ok, when a user chooses that form for the first time, after
opening a document. But, if the one tries to choose that form a second time,
then for some weird reason, a command button transforms into a picture. It
still has command button properties, but behaves like a picture. When you
click it, it shows a selection, like if you have selected a picture, not a
button. No actual CommandButton_Click executed. If you go to properties of
that button, you will have the normal command button properties. If you try
to resize it, my Word 2007 crashes totally.

Any suggestions?

 

[Alexander]

Forgot to mention my specs:
Microsoft Office Word 2007 (12.0.6504.5000) SP2 MSO (12.0.6425.1000)
Microsoft Windows XP SP3

 

[Alexander]

Hi,

Well, it gets more complicated now... I have tried to solve this issue with
a workaround, by calling a custom userform, when this form is selected from
the drop down list. Userform contains organized simple labels that contain
the policy text and a command button that allow to accept the policies. A
macro code hides the userform upon the Accept button pressing. It was ok in
the beginning, but at some point Word just crashed. Similar to what happened
when I tried to resize a button in the initial report. The problem now is
that the whole document cannot be opened. It gives an error message upon
opening with the error report sending and stuff. After the report is sent, it
automatically tries to restore the document and open it. But fails. It shows
a blank document and in a few seconds the same error appears. Word falls into
this error/restart/error/reastart loop. More of that, I cannot open Word at
all now. Going to Word shortcut in Start menu to create a new blank document
gives the same error loop. Word crashes upon start in Safe Mode even. Thats
not all, PowerPoint and Excel has stopped opening now as well, giving the
same error loop.

I am sad to lose my template, and the time spent on it. But please, check
this issue out, as it might affect the some people's business processes quite
heavily due known reasons. As of now I have to request our servicedesk to
reinstall my office package. Hope it helps

Please, feel free to request further details. I am ready to provide my full
support.

Alex

 

[Alexander]

Just to mention: rebooting PC and recreating the word data key does not help.
Alex

 

[Alexander]

Here is what I have found so far:
When a document fails to be opened and the word crashes, next time it asks
if I want to open it in safe mode. Choosing yes does not help. Word crashes
anyway. It actually crashes even I don't give an answer within a few seconds.
So, I thought that safe mode also doesn't work. But it actually works, if I
run winword /a command. Word opens in safe mode and from there I can open my
template document. I removed the custom userform hoping it would solve the
issue, but it didn't. Word/Excel/PPT crash upon starting in normal mode.
I also run the Microsoft Office Diagnostics, but it didn't find any problems.

Alex

 

[Alexander]

I could solve the issue with opening the Office applications after studying
the error message.

AppName: winword.exe
AppVer: 12.0.6504.5000
AppStamp: 49e7f5b6
ModName: olconnector.dll
ModVer: 2.0.3009.0
ModStamp: 4a2e1608
fDebug: 0
Offset: 00011561

I removed the Office Live Add-in 1.4 from my PC and it solved the problem.
Although its not the best solution, but acceptable for my case.

The initial problem with storing the command button in the Quick Parts is
still a question. I will try to use the custom user forms again...

Rgds,
Alex