Rich - I would do it this way, but what happens is when the Host computer is not responding message comes up, it is some sort of seperate message window from the actual workstation program and not meditech itself. I can't figure out a way to check for this window. The other problem that I run into is once I click ok (the only option) on this box the screen clears and the display is all screwed up so it doesn't know what is going on other than the cursor is now in the top left hand corner of the screen. It seems to follow whatever template was on the screen when it happened, but the screen doesn't fix itself until you actually log out of Meditech and back in. If I could figure out a way to detect when this box comes up I could send the keys to cancel the current report and just re-enter all the info again fairly easily.
John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rich McNeil Sent: Tuesday, December 23, 2003 12:31 PM To: [EMAIL PROTECTED] Subject: RE: [Talk] Meditech - Host Computer not Responding message I know this is not good news, but I think you'll need to slow down the keying. I've seen this happen on old serial connections, but I see it's also possible when any communication channel is overflowed. Perhaps a better approach is to let it fail...and if it fails for this reason, try it again...if it still fails...slow it down. Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hayman Sent: Tuesday, December 23, 2003 12:56 PM To: [EMAIL PROTECTED] Subject: [Talk] Meditech - Host Computer not Responding message Has anyone come up with a good way of trapping the "Host computer is not responding" message from Meditech or better yet, preventing it? It only happens when I am enter text into the free text area of OE via the script. Apparently it sends this message when Meditech is not able to keep up with the data being sent. I don't get it all the time, but it seems when the network is running slow it does this. Thanks in advance, John
