BUG: SET MESSAGE WINDOW Command Not Working Correctly

 Last reviewed: May 6, 1997
Article ID: Q108609
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0, 5.0, 5.0a
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, and 2.5b
  • Microsoft FoxPro for MS-DOS, versions 2.0, 2.5, 2.5a, and 2.5b

SYMPTOMS

The SET MESSAGE WINDOW [<window name>] command does not work as expected.

This command is supposed to let you specify where to display messages created with the WAIT, @ ... PROMPT, DEFINE BAR, DEFINE MENU, DEFINE PAD, and DEFINE POPUP commands. It cannot be used to control the placement of a WAIT WINDOW.

The following program demonstrates the intended usage of the SET MESSAGE WINDOW command: 

   DEFINE WINDOW X FROM 20,20 TO 23,65
   ACTIVATE WINDOW X
   SET MESSAGE WINDOW X
   WAIT 'Check out the location of this message!'
   RELEASE WINDOW x
   CLEAR
   SET MESSAGE WINDOW && Resets SET MESSAGE WINDOW to the default
   WAIT 'Now look where the message appears by default'
However, if you eliminate both SET MESSAGE WINDOW lines from this code sample, the program performs no differently.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords : buglist2.00 buglist2.50 buglist2.50a buglist2.50b vfpbug5.0a kbbuglist
Version : 2.5 2.5a 2.5b 3.0 5.0 5.0a
Platform : MS-DOS WINDOWS
Issue type : kbbug

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