FIX: EVALUATE() Causes Error Message in Group Expression

Last reviewed: October 14, 1997
Article ID: Q107399
2.50a WINDOWS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.5a

SYMPTOMS

Using the EVALUATE() function in a group expression in the Report Writer may generate the error message "Invalid function argument value, type or count."

STATUS

Microsoft has confirmed this to be a problem in FoxPro 2.5a for Windows. This problem was corrected in FoxPro 2.5b for Windows.

MORE INFORMATION

Steps to Reproduce Problem

These steps assume that you have installed the tutorial files for FoxPro and that the main FoxPro directory is called C:\FOXPROW.

  1. In the Command window, type the commands:

          SET DEFAULT TO C:\FOXPROW\TUTORIAL
          USE detail
          CREATE REPORT
    

  2. From the Report menu select Quick Report, accept the defaults, and choose OK.

  3. From the Report menu, choose Data Grouping.

  4. Choose the Add button and type the following in the Group field:

          EVALUATE(memvar)
    

  5. Choose OK to return to the Data Grouping dialog box. Then choose OK again.

  6. In the Command window, type:

          memvar=“LEFT(pno,3)”
    

  7. From the Report menu, choose Page Preview.

You will receive the error message mentioned above.


Additional reference words: FoxWin 2.50a buglist2.50a fixlist2.50b RWriter
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FxtoolRwriter
Solution Type : kbfix


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: October 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.