I reported the error via the Managed Newsgroups, and in December was
informed that it was caused by a particular version of FM20.dll which had
been installed via hotfix 950278. I removed the fix, and the problem went
away.
Yesterday I revisited the relevant code, and found the problem has returned.
This is presumably due to maintenance automatically appllied via Windows
Update sometime since December. I suspect the most likely candidate is the
SP2 update toOffice 2007. For your info, my present FM20.dll level is
12.0.6415.1000.
If you still have access to the managed newsgroups, report it again. I'll put it
in through MSDN Connect.
--
Regards,
Jay Freedman
Microsoft Word MVP FAQ: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so all
may benefit.
On Sat, 9 May 2009 01:38:01 -0700, Julian Ladbury <jlad...@nospam.nospam>
wrote:
I can also see the problem. I will report this internally. Hopefully, this
break will be fixed in the next version of FM20.dll.
Currently, as a temporary solution, we need to use back to the
12.0.6211.1000 version FM20.dll. Please perform the following steps in your
side,
1 Right click the command prompt and click Run As Administrator.
2 Navigate to C:\Windows\System32 (It should be the default path)
2 Type "regsvr32 /u FM20.dll" and press Enter.
3 In the windows explorer, delete the 12.0.6415.1000 FM20.dll from
C:\Windows\System32
4 Copy the 12.0.6211.1000 FM20.dll into C:\Windows\System32
5 In the command window, type "regsvr32 FM20.dll" and press Enter.
After performing the above steps, I resolve the issue in my side. Please
let me know if this fixes the issue for you. For your convenience, I upload
a 12.0.6211.1000 version FM20.dll in my SkyDrive which you can download.
After you download it, you need unblock it from the property page.
http://cid-c2e0d62e8a095a30.skydrive.live.com/self.aspx/Public/FM20.zip
Best regards,
Colbert Zhou (colbertz @online.microsoft.com, remove 'online.')
Microsoft Online Community Support
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd...@microsoft.com.
As this does not cause me any grief in my own environment I will not take
the time to regress FM20.dll. However, it does have the potential to affect
prospective customers, who might encounter this error when evaluating my
product. I hope that Microsoft will appreciate that this bug has the
potential adversely to affect their partners' sales, and will ensure that it
is fixed as soon as possible. It is now 6 months since I first reported the
bug on MSDN, and I would have hoped that the development team would have
fixed it by now.
Fortunately, the bug only affects my prospective customers, not my current
ones. Sadly that is not the case for everyone, as the following post shows:
http://www.eggheadcafe.com/conversation.aspx?messageid=34415284&threadid=33410274.
Please let me know how Microsoft will proceed with this - a little more
detail than 'hopefully it will be fixed in the next version. . .' would be
appreciated.
"Colbert Zhou [MSFT]" <colb...@online.microsoft.com> wrote in message
news:3AtZs17...@TK2MSFTNGHUB02.phx.gbl...
colbert wrote:
The product team has opened a bug for this issue.
21-May-09
The product team has opened a bug for this issue. The issue is scheduled to
be fixed in the Office 2007 SP3 in our database. Hope the information will
help for the community members who are facing the
Previous Posts In This Thread:
On 09 May 2009 04:29
JulianLadbur wrote:
textbox.curline=0 gives runtime error -2147418113
I have a Word application which includes a text box on a form. When the form
opens, it sets Curline=0 in the text box. This worked without problem for
some years. Last November it began to give the er
On 09 May 2009 04:38
jladbur wrote:
RE: textbox.curline=0 gives runtime error -2147418113
Posting a reply with the correct nospam alias . ..
"Julian Ladbury" wrote:
On 09 May 2009 13:23
Jay Freedman wrote:
I see the same behavior, and it's with the same version of FM20.dll.
I see the same behavior, and it is with the same version of FM20.dll. That is
indeed the version from Office 2007 SP2.
If you still have access to the managed newsgroups, report it again. I will put
On 13 May 2009 07:24
colbert wrote:
Hello Julian, I can also see the problem. I will report this internally.
Hello Julian,
I can also see the problem. I will report this internally. Hopefully, this
break will be fixed in the next version of FM20.dll.
Currently, as a temporary solution, we need to use back
On 13 May 2009 08:57
Julian Ladbury wrote:
Thank you Colbert.
Thank you Colbert.
As this does not cause me any grief in my own environment I will not take
the time to regress FM20.dll. However, it does have the potential to affect
prospective customers, who mig
On 21 May 2009 07:29
colbert wrote:
The product team has opened a bug for this issue.
The product team has opened a bug for this issue. The issue is scheduled to
be fixed in the Office 2007 SP3 in our database. Hope the information will
help for the community members who are facing the
EggHeadCafe - Software Developer Portal of Choice
Using the Intercepting Filter Pattern to create a Generic Reusable Processing Pipeline
http://www.eggheadcafe.com/tutorials/aspnet/ce017b7f-19e5-4586-b227-c7f21cbe1b3c/using-the-intercepting-fi.aspx
That hotfix should be for other issues which updates the FM20.dll. As I
mentioned in previous reply. The Word PG has already known this issue and
they will fix it in the Word 2007 SP3 as scheduled. :-) Thanks for your
patience and have a nice day, Sir!
Best regards,
Ji Zhou
Microsoft Online Community Support