filePro with no stdin (was Re: Hosting filePro applications)

[Cole, Ken (ABRC)]

> [...]
> > If it happens in 5.0.14, I have no real reason to believe
> it was fixed
> > in the upcoming 5.6 unless told otherwise.  Someone in the beta
> > program would have to test that.
>
> Well, now that the condition has been identified, it can be fixed.
>
> Of course, the question becomes "what should filePro do if it
> needs input and stdin is closed or at EOF?"

If by input you mean "waiting for a return/enter after an error" then
terminate immediately and write/append the details to a log file would
be my first reaction.

Ken

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************