Microsoft KB Archive/823990

= Corrections to Help Topics for Visual Studio Tools for Office =

Article ID: 823990

Article Last Modified on 10/23/2006

-

APPLIES TO


 * Microsoft Office Professional Edition 2003
 * Microsoft Visual Studio Tools for the Microsoft Office System version 2003

-





SUMMARY
This article contains corrections for known errors in the Microsoft Visual Studio Tools for the Microsoft Office System Help topics.



MORE INFORMATION
The list of known errors and their corrections follows:  === How To: Automatically Fill Ranges with Incrementally Changing Data ===

The code sample that follows for the Microsoft Visual Basic .NET example does not qualify the xlAutoFillType property: Private Sub AutoFill Dim rng As Excel.Range = ThisApplication.Range(&quot;B1&quot;) rng.AutoFill(ThisApplication.Range(&quot;B1:B5&quot;), _       XlAutoFillType.xlFillWeekdays)

rng = ThisApplication.Range(&quot;C1&quot;) rng.AutoFill(ThisApplication.Range(&quot;C1:C5&quot;), _       XlAutoFillType.xlFillMonths)

rng = ThisApplication.Range(&quot;D1:D2&quot;) rng.AutoFill(ThisApplication.Range(&quot;D1:D5&quot;), _       XlAutoFillType.xlFillSeries) End Sub Change the previous code to the following code: Private Sub AutoFill Dim rng As Excel.Range = ThisApplication.Range(&quot;B1&quot;) rng.AutoFill(ThisApplication.Range(&quot;B1:B5&quot;), _       Excel.XlAutoFillType.xlFillWeekdays)

rng = ThisApplication.Range(&quot;C1&quot;) rng.AutoFill(ThisApplication.Range(&quot;C1:C5&quot;), _       Excel.XlAutoFillType.xlFillMonths)

rng = ThisApplication.Range(&quot;D1:D2&quot;) rng.AutoFill(ThisApplication.Range(&quot;D1:D5&quot;), _       Excel.XlAutoFillType.xlFillSeries) End Sub  === How To: Update Deployed Office Documents ===

The Microsoft Visual C# .NET code that is documented in this topic does not compile because the compiler detects an incomplete escape sequence. To correctly display a backslash in a Visual C# .NET string, use the escape sequence (\\) in the string or start the string with an ampersand (@) character to indicate that the string must be interpreted verbatim. To correct the compile error, replace the code in this topic with either of the following code samples:   MessageBox.Show(&quot;This document has been updated. Download a new version from the following location: \\\\ServerName\\FolderName&quot;);   MessageBox.Show(@&quot;This document has been updated. Download a new version from the following location: \\ServerName\FolderName&quot;);   === Excel Application Object Functions, Windows, and Names ===

The dblAverage variable that is used in the following code sample is not declared and may produce a compile error.

Methods generally accept up to thirty-two parameters. Therefore, if you want to calculate the average of a fixed list of numbers, you can use code that is similar to the following Visual Basic syntax: dblAverage = ThisApplication.WorksheetFunction.Average( _   12, 14, 13, 19, 21) To correct this error, declare dblAverage as a Double type: Dim dblAverage as Double = ThisApplication.WorksheetFunction.Average( _   12, 14, 13, 19, 21)  === Walkthrough: Updating a Chart in a Worksheet Using Option Buttons ===

The &quot;Add References&quot; section that is included in this topic contains an unnecessary step for referencing the Microsoft Graph Primary Interop Assembly (PIA). The Microsoft Excel chart feature does not require Graph. Therefore, a reference to the Graph PIA is unnecessary.

If you omit the Graph PIA reference, you must also omit the Graph PIA namespace statement from the code. You can omit the following namespace statements in the &quot;Adding Namespace Statements and Declaring Class-Level Variables&quot; section: ' Visual Basic Imports Graph = Microsoft.Office.Interop.Graph

// C# using Graph = Microsoft.Office.Interop.Graph; </li> === Walkthroughs Contain Unnecessary Steps for Adding a Reference to MSForms ===

Several of the walkthroughs instruct you to add a reference to the MSForms 2.0 PIA and a corresponding namespace statement. However, the MSForms 2.0 PIA is automatically referenced when you create a new Office project, and the corresponding namespace statement is automatically added for you. Therefore, these steps in the walkthroughs are unnecessary and can be omitted. </li></ul>

Keywords: kbofficeauto kbhelpfile kbdocs kbdevstudio kbinfo kbdocerr kbarttypedocerr kbpending KB823990

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.