BUG: FoxDoc XREF.DOC Contains Variables 1] and 2]

 Last reviewed: April 30, 1996
Article ID: Q115053
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6

SYMPTOMS

The FoxDoc XREF.DOC file will contain variables "1]" and/or "2]" (without the quotation marks) at the top of the documented variables list for a program if the program contains arrays.

CAUSE

The REPORTS.SPR file in the ACCNTS project contains the line: 

   reps[i,2] = " "+reps[i,1]+" .. "+reps[i,2]
If FoxDoc is asked to produce an XREF.DOC file on either this report or on the ACCTS.PJX file, which contains this report, the variables "1]" and "2]" will appear at the beginning of the list. FoxDoc is misinterpreting this array statement because commas are usually used to separate cross-reference words.

If another program is called from a program containing these array statements, it may also be erroneously included under these variables.

RESOLUTION

Ignore these entries. The rest of the variables in the program are listed below these erroneous entries.

STATUS

Microsoft has confirmed this to be a problem in FoxPro versions 2.5, 2.5a, 2.5b, and 2.6 for Windows. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional reference words: FoxWin 2.50 2.50a 2.50b 2.60 buglist2.50
buglist2.50a
buglist2.50b buglist2.60
KBCategory: kbenv kbdocerr kbbuglist
KBSubcategory: FxtoolFoxdoc

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 30, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.