Hi Tom,

First of all you, as you will see in help, the @x,y SAY syntax is no longer recommended. It is partly supported, for backward compatibility, but 'at your own risk' to say it like that.

If you don't want to rewrite your code, you will probably get your program to work by trying different values for the SIZE parameter of the @x,y SAY command.

>Hi
>
>I'm seeing some really bizarre behavior when using @ ... Get, @ ... Say commands with VFP8 on a factory install of Windows XP. I'm not having this problem in other environments (VFP7+XP is fine, VFP8+Windows200 is fine). Also computers upgraded to XP from an older version of windows do not have this problem, either.
>
>Simple code like the following is causing problems:
>
>-----------------------------
>DEFINE WINDOW blah FROM 1,1 TO 8,60
>ACTIVATE WINDOW blah
>@ 1,2 say 'TEXTBOX' get xxx
>@ row()+2, col() say 'OPTION' get yyy pict '@*RHN one;two;three;four'
>@ row()+2, 2 say 'DROPDOWN' get yyy pict '@*RHN one;two;three;four'
>READ
>
>DEACTIVATE WINDOW blah
>-----------------------------
>
>The window displays fine with the controls just as you would expect. However, when the mouse is placed over the the DROPDOWN control or the OPTION control, everything in the Window dissapears (the TEXTBOX control is fine, as well as Listbox-style control). Hovering over the control with the mouse will display the control again, but any static text is gone.
>
>The controls function properly when clicked, but they're just not visible on the screen until the mouse is hovered over them.
>
>Has anyone seen this before? Or have a solution (other than rewriting the code to use VFP Forms)?
>
>Thanks for your help
>
>Tom Bellin