Nevermind... I see that it was program code that was visible NOT output.
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Karen
> Tellef
> Sent: Thursday, October 09, 2014 10:05 AM
> To: RBASE-L Mailing List
> Subject: [RBASE-L] - Strange DOS behavior
>
> This is not a problem -- it was resolved by simply starting the RBase
> session. But I'm curious if anyone can think of an explanation of why
> this happened. The client sent me a print-screen, otherwise I wouldn't
> believe it...
>
> As mentioned in the subject, they're running DOS (most of the app is in
> windows, one module still in DOS). This happened on just one
> workstation running a common program, all other workstations ran the
> same program and didn't show the behavior.
>
> The program has several user prompts and a form. Behind the user
> prompts and forms, you can see program code, as if a 'SET ECHO ON'
> command was run. It wasn't in trace mode because they didn't have to
> press any keys to advance thru the code. I did a search of all program
> code and custom eeps, and not a single instance of an "echo" command.
> Of course, if there was an "echo" in a program then all workstations
> would have had the issue....
>
> So other than an Echo, is there anything workstation-specific that
> would cause all the program code to display in the background? Any
> other RBase command I can search for? Or was this the result of
> something happening outside RBase? Hasn't happened before, nor
> since....
>
> Puzzle of the day!
>
> Karen
>
>
>
