When I monitor the process, this situation seems to occur when it is stuck at an uknown prompt (unknown to the data entry process). I will try this idea. Thank you.
________________________________ From: [EMAIL PROTECTED] on behalf of Rich McNeil Sent: Wed 7/27/2005 5:29 PM To: [email protected] Subject: RE: [Talk] Windows Being left open Osar, The Disconnect method in Meditech send a Windows CLOSE message to the Remote WorkStation. There may be times that it's busy or not listening. You might try multiple Disconnects spaced out over a second or two. Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Osar, Eric Sent: Wednesday, July 27, 2005 2:05 PM To: [email protected] Subject: [Talk] Windows Being left open I am using BWS to interface with Meditech Workstation 3 client. The program is basically an automated data entry system that is constantly running. In the event that the application comes across an unknown prompt, the application will timeout and attempt to close the Meditech connection and start a new session in Meditech. On some occasions, the disconnect method in BWS does not seem to close out the window. Does anyone know how to correct this issue? Basically, I need to be able to close the Meditech window in these instances so I do not have multiple windows sitting open using up server resources. Any ideas would be appreciated. Thanks Eric R. Osar
<<winmail.dat>>
