We try to avoid CPU overload by using Sleeps and DoEvents in our Pause's and Wait's, and usually the scripting engine can be kept below 5 percent or even 1 percent while it's running.
If the application has shutdown, you'll need logic in your script to detect the shutdown and then either restart the app or halt the script. Some straightforward ways to detect an application is to use our Active command or to try to Activate it using the Caption. Another alternative is to use our BootMgr which will reboot the PC if the script becomes inactive in some fashion. It's save us from a lot of 2 am support calls. Can we get more details on the OR application? Rich McNeil Boston Software Systems 866 653 5105 www.bostonworkstation.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of White,Scott A Sent: Monday, December 29, 2003 3:28 PM To: '[EMAIL PROTECTED]' Subject: [Talk] BWS taking up ALL resources Hello everyone, Has anyone else ran into this problem with the "server" they are running the BWS Runtime software on? A couple times a week we have to remote into the server that our OR uses to run their billing script to kill of the BSS65.exe. This has ocurred 8 times since installing BWS on our Server. It is almost always associated with an improper sign off by our users; but I'd like to know if anyone is aware of a patch that prevents BWS from eating up 77%-90% of the resources. Re-training the users to properly close the apps. before signing off is becoming inane. We are "investigating" the use of a script that "Violently" closes all apps. running on that session when the user signs off correctly. Any suggestions you have would be appreciated. Thank you, Scott CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify Saratoga Hospital immediately by e-mail at [EMAIL PROTECTED] and destroy all copies of this communication and any attachments.
