textbox.curline=0 gives runtime error -2147418113 (8000ffff)

[Julian Ladbury]

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 has worked without problem for
some years. Recently it has begun to give the error mentioned, on just one of
my machines. The failing machine is running Vista Home Premium SP1, Office
2007 SP1 with all MS Update maintenance applied automatically.

I can provide a test Word document to recreate the error.

Soemone else has repiorted the same problem - see
http://www.microsoft.com/communitie...eral&mid=8681d558-2232-4dc1-9f74-efa6ce011139.

 

[\Ji Zhou [MSFT]\]

Hello Julian,

Thanks for using Microsoft Newsgroup Support Service, this is Ji Zhou
[MSFT] and I will be working on this issue with you. I am sorry for that
you are suffering from the unflagged issue.

As to the issue, I have tested with a few of machines on my side. The
result is quite different and strange. The following is the detailed,

Reproduced environments,

*Two machines with Windows Server 2008 SP1, Office 2007 SP1
*One machine with Vista Enterprise SP1, Office 2007 SP1
*One machine with Vista Enterprise, Office 2007 SP1

No Reproduced environments,

*Two machines with Vista Enterprise SP1, Office 2007 SP1
*One machine with Windows Server 2003, Office 2007 SP1

This issue seems to be OS environment related. And as you know, for the
Office application and FM20.dll symbols are not provided, it is hard to
debug and find what the problem is there. But I have already consulted the
Office Product Team to see if anyone can help to investigate this issue. Of
course, I am still doing future more research on this.

And currently I have found that the error only happens when we are trying
to set the Curline property to 0. If we are setting the Curline property to
1, the codes will work correctly. So may I suggest the following approach
as a workaround at this time. And if I have got a reply from the product
team, I will inform you as soon as possible.

------My Workaround-----
Replace the following line,

Me.TextBox1.CurLine = 0

with

Me.TextBox1.CurLine = 1
SendKeys "{UP}"

So when the Form is opened, the cursor will locate at firstline.

Hope this helps more or less! Have a nice day!


Best regards,
Ji Zhou ([email protected], 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:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Julian Ladbury]

Ji Zhou,

Thank you for a speedy response and for the suggested workaround.

Sadly my code has already been published, and I will not be able to
incorporate the workaround until the next release, which I do not anticipate
for a matter of months.

In the mean time, I would be grateful to know exactly what the cause is once
you have found out, as I will then be able to inform any of my customers who
encounter this error.

Hello Julian,

Thanks for using Microsoft Newsgroup Support Service, this is Ji Zhou
[MSFT] and I will be working on this issue with you. I am sorry for that
you are suffering from the unflagged issue.

As to the issue, I have tested with a few of machines on my side. The
result is quite different and strange. The following is the detailed,

Reproduced environments,

*Two machines with Windows Server 2008 SP1, Office 2007 SP1
*One machine with Vista Enterprise SP1, Office 2007 SP1
*One machine with Vista Enterprise, Office 2007 SP1

No Reproduced environments,

*Two machines with Vista Enterprise SP1, Office 2007 SP1
*One machine with Windows Server 2003, Office 2007 SP1

This issue seems to be OS environment related. And as you know, for the
Office application and FM20.dll symbols are not provided, it is hard to
debug and find what the problem is there. But I have already consulted the
Office Product Team to see if anyone can help to investigate this issue. Of
course, I am still doing future more research on this.

And currently I have found that the error only happens when we are trying
to set the Curline property to 0. If we are setting the Curline property to
1, the codes will work correctly. So may I suggest the following approach
as a workaround at this time. And if I have got a reply from the product
team, I will inform you as soon as possible.

------My Workaround-----
Replace the following line,

Me.TextBox1.CurLine = 0

with

Me.TextBox1.CurLine = 1
SendKeys "{UP}"

So when the Form is opened, the cursor will locate at firstline.

Hope this helps more or less! Have a nice day!


Best regards,
Ji Zhou ([email protected], 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:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Julian Ladbury]

Ji Zhou,
I would appreciate an update to the current status of this problem - whether
the root cause has been identified, and when a fix might be released.
Julian

Hello Julian,

Thanks for using Microsoft Newsgroup Support Service, this is Ji Zhou
[MSFT] and I will be working on this issue with you. I am sorry for that
you are suffering from the unflagged issue.

As to the issue, I have tested with a few of machines on my side. The
result is quite different and strange. The following is the detailed,

Reproduced environments,

*Two machines with Windows Server 2008 SP1, Office 2007 SP1
*One machine with Vista Enterprise SP1, Office 2007 SP1
*One machine with Vista Enterprise, Office 2007 SP1

No Reproduced environments,

*Two machines with Vista Enterprise SP1, Office 2007 SP1
*One machine with Windows Server 2003, Office 2007 SP1

This issue seems to be OS environment related. And as you know, for the
Office application and FM20.dll symbols are not provided, it is hard to
debug and find what the problem is there. But I have already consulted the
Office Product Team to see if anyone can help to investigate this issue. Of
course, I am still doing future more research on this.

And currently I have found that the error only happens when we are trying
to set the Curline property to 0. If we are setting the Curline property to
1, the codes will work correctly. So may I suggest the following approach
as a workaround at this time. And if I have got a reply from the product
team, I will inform you as soon as possible.

------My Workaround-----
Replace the following line,

Me.TextBox1.CurLine = 0

with

Me.TextBox1.CurLine = 1
SendKeys "{UP}"

So when the Form is opened, the cursor will locate at firstline.

Hope this helps more or less! Have a nice day!


Best regards,
Ji Zhou ([email protected], 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:
(e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[\Ji Zhou [MSFT]\]

Hello Julian,

I am very sorry for following up this thread late. Based on my research, it
proves that the issue is caused from the different version of FM20.dll.

I have used Windbg to print out the dll versions in both of the working
machine and the problematical machine. I find that,

*In the machine that can reproduce the issue, the FM20.dll version is
12.0.6307.5000
*In the machine that cannot reproduce the issue, the FM20.dll version is
lower, like 12.0.6211.1000

After searching on the web, I find that the FM20.dll 12.0.6307.5000 is
included in a hotfix(2008/5/2) to resolve an Office 2003 issue. The related
KB article is here http://support.microsoft.com/kb/950278. So, to avoid our
issue, we just need to remove this hotfix from your customer's machine.

To do so,

1.From the desktop, click the Start->Run, input the "Control Panel" and
click OK.

2.Double click the "Program and Features".

3.In the left panel, click the "View installed updates",

4.In the updates list, find all "Hotfix for Office(KB 950278)", uninstall
them.

This should fix our problem. If our Office version is 2007, then please
feel free to uninstall this hotfix since it is used to fix an Office 2003
issue described in the above KB. I have also reported this issue internally
but did not get reply at this time, so not very sure when it will be fixed.
I will inform you as soon as possible if I get the product team's
confirmation.

Have a nice day!


Best regards,
Ji Zhou ([email protected], 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:
(e-mail address removed).

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Julian Ladbury]

Thanks Ji Zhou. I have uninstalled the hotfix and can confirm that the
problem has gone away. Once again, thank you for an excellent service.