RDP and @Say definately have problems. We have 1 oldstyle app we now run for a customer in our server farm. RDP from 1 machine is rock solid, but when the RDP session running on the server is switched between different local machines, chances are that you see the frame of the 2.6 window after switch, everything else blanked out. Issueing the analogous repaint-function generated by 2.6 screen tools will show you the @get fields, but not the @say.

This happens here when different local screen resolutions RDP into the session. As we know those screens in our sleep, no further fix attempts were done.


>Hi!
>
>>Most probable, IMO, is that the app is not responding to periodic querying by Windows, so it considers the app dead or crashed.
>
>(not responding) does not appear in title bar.
>So maybe VFP does not redraw screen if output is created using ? commands.
>
>>Include a DOEVENTS FORCE somewhere, preferrably on a timer. In my experience, the timer's interval should be somewhat >shorter than 5 seconds.
>>In my case it was the long conversion routines, which would repackage tens of thousands of records from an outside source into the SQL database, and the usual echoing of log on _screen and periodic wait window nowait aren't considered signs of activity, so I'd get the milk-over-app whitish display, and the app would be labeled as "not responding". It stopped when I added this in the same periodic check. Just didn't put the check on each 100 records, but rather on every 10 and if number of seconds since last Doevents was >4,56 (which is my guesstimate, not from any documentation).
>
>This is console style application is running from mobile phones using iTap RDP client.
>It uses wait and accept commands for user input.
>
>Are you sure that VFP timer even fires if application waits input from ACCEPT command?
>
>Or maybe application can re-factored so that it re-draws screen properly under RDP ?
>Application needs two commands:
>
>1. ? - Write line to screen
>2. ACCEPT - Read line from screen. Backspace key should delete previous character and enter should pass input string
>to caller.
>
>Maybe SAY/GET or writing using other methods should work.
>Where to find console window implementation in VFP using other commands, not ? and accept ?
>
>ACCEPT command uses hard-coded 9 pt FoxFont font for input. Using other command can allow to increase input font size also.