Microsoft KB Archive/212562

= WD2000: Run-time Error '5941' Using Border Constants with Font.Borders =

Article ID: 212562

Article Last Modified on 9/12/2006

-

APPLIES TO


 * Microsoft Word 2000 Standard Edition

-



This article was previously published under Q212562





SYMPTOMS
When you attempt to apply borders to selected characters using Microsoft Visual Basic for Applications, the following error message may appear:

Run-time error '5941':

The requested member of the collection does not exist.



CAUSE
By design, character borders only take 1 or the wdBorderTop constant as arguments, because the character borders count equals 1.

For example, the following Visual Basic for Applications commands cause the error to occur if you attempt to designate a right border for a selected character: Selection.Font.Borders(wdBorderRight).LineStyle _ =WdLineStyleThickThinSmallGap



WORKAROUND
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

For more information about how to use the sample code in this article, click the article number below to view the article in the Microsoft Knowledge Base:

212536 OFF2000: How to Run Sample Code from Knowledge Base Articles

To work around this problem, use either of the following lines of code to apply the border style to a selected character: Selection.Font.Borders(1).LineStyle = WdLineStyleThickThinSmallGap

-or-

Selection.Font.Borders(wdBorderTop).LineStyle = _ WdLineStyleThickThinSmallGap



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

