Paul - I am sending in straight text in large strings that range in size from a paragraph to 6 or 7 pages worth of data. There aren't really any natural breaks in it but I guess I could put together a command to chop the string up every x # of characters. I am afraid that even if I do that, it will still error out if it happens to be slow at the moment the string is spit into Meditech. The only reliable solution that I could come up with would be to send a character, wait, send a character, etc. which would lead to a VERY slow process for the large amounts of data that we are sending in.
John -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Donoughe Sent: Tuesday, December 23, 2003 12:15 PM To: [EMAIL PROTECTED] Subject: RE: [Talk] Meditech - Host Computer not Responding message John just some thoughts. If your script is slamming data in, you might want to use the "Pause" command. The pause command will wait until the cursor gets to a specified location, and then will continue moving. What's nice is that the Pause does not cause any unnecessary delays like stable or wait. If you know the cursor will always be at a certain column location, but not a specific row once it's done slamming something in, you can use Pause("@0,10") if 10 was the column number. Another idea.. If you're slamming in large strings, you might want to break them into smaller chunks. If all else fails, use the stable command. Paul -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hayman Sent: Tuesday, December 23, 2003 9:56 AM 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
