S
sparrow_ce
Have researched this error and not finding solution. I have a Word form with
VB Buttons and code, when I open it on my desktop and enable the macros it
works fine. I emailed it to a remote location (we use Office 2002, SP3, they
are 2003, SP2 - our mail client is Lotus Notes, theirs Outlook) and it worked
ok for them. However, when they edited it and emailed it back to me, I could
not get it to exit design mode, and somehow the vb button names had gotten
mixed up, with a 1 at the end of each button name. I emailed them back
exactly the same form they sent me that acted corrupted for me, with no
revisions, and it worked fine for them. The original one worked fine for me.
So I'm suspicious of office/OS compatability issues and we have hundreds of
users affected who use this Word form and lately there have been instances of
'corrupted' documents. Having a hard time isolating cause.
My work around is to open a blank shell of the template that I keep on hand
for repairs, it has all the vb forms in it, etc., and I paste the corrupted
doc into the shell, then rename the vb buttons. Won't let me rename in the
original document, says 'ambiguous name detected', but can't find the vb
button with the original name.
Is it possible for things to happen in the email transport of the document?
Also, we are both with large firms whose IT departments have customized the
Office/OS loads for their own security/other concerns, and it's possible
something in the loads of our machines is missing on one side or the other
causing this problem.
If so, what files/other things would I need to look for or ask IT to put
back into our load, if that is the case.
Hope this makes sense, please let me know if you need more information.
VB Buttons and code, when I open it on my desktop and enable the macros it
works fine. I emailed it to a remote location (we use Office 2002, SP3, they
are 2003, SP2 - our mail client is Lotus Notes, theirs Outlook) and it worked
ok for them. However, when they edited it and emailed it back to me, I could
not get it to exit design mode, and somehow the vb button names had gotten
mixed up, with a 1 at the end of each button name. I emailed them back
exactly the same form they sent me that acted corrupted for me, with no
revisions, and it worked fine for them. The original one worked fine for me.
So I'm suspicious of office/OS compatability issues and we have hundreds of
users affected who use this Word form and lately there have been instances of
'corrupted' documents. Having a hard time isolating cause.
My work around is to open a blank shell of the template that I keep on hand
for repairs, it has all the vb forms in it, etc., and I paste the corrupted
doc into the shell, then rename the vb buttons. Won't let me rename in the
original document, says 'ambiguous name detected', but can't find the vb
button with the original name.
Is it possible for things to happen in the email transport of the document?
Also, we are both with large firms whose IT departments have customized the
Office/OS loads for their own security/other concerns, and it's possible
something in the loads of our machines is missing on one side or the other
causing this problem.
If so, what files/other things would I need to look for or ask IT to put
back into our load, if that is the case.
Hope this makes sense, please let me know if you need more information.