BUG: Fourth RGB() COLOR Pair in @ ... SAY Gives Syntax Error

Last reviewed: June 27, 1995
Article ID: Q118559
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6

SYMPTOMS

When issuing an @ ... SAY with a COLOR clause containing RGB() function color specifications, you get a "Syntax Error" message.

CAUSE

This error message is caused by the RGB() function color in the fourth color pair slot.

RESOLUTION

If you remove the RGB() function in the fourth slot, you will not get an error [even if you have RGB() functions in slots 5-10]. In addition, you will not receive an error if you are using the one character color specification, for example R/W, in all of the slots instead of the RGB() color specification.

STATUS

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

MORE INFORMATION

Steps to Reproduce Problem

To reproduce this problem, create a program containing the following code:

   @ 4.813,3.250 SAY "Float_:" ;
        SIZE 1.000,11.000 ;
        FONT "MS Sans Serif", 8 ;
        STYLE "T" ;
        COLOR RGB(,,,255,255,255),RGB(,,,255,0,255),;
             RGB(0,0,0,,,),RGB(0,0,0,255,255,255)


Additional reference words: FoxWin 2.50 2.50a 2.50b 2.60 buglist2.50
buglist2.50a
buglist2.50b buglist2.60 errmsg err msg
KBCategory: kbprg kberrmsg kbbuglist
KBSubcategory: FxprgGeneral


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: June 27, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.