Greetings! I'm using procedural scripting and am fairly new to VB and BW, though I am familiar with the logic of programming in general.
C:\BW Code\Ops Code\Main Ops.bws is the collection of scripts I'm using. This was predesigned by a coworker so I'm not sure what the file actually is, only that it opens BW and controls the scripts within it. I've successfully used his scripts to create new ones within the same area, and they work fine (most of the time). My problem is that the scripts within are not yet error-detecting enough to avoid stalling on occasion when weird things happen. I was hoping to find some way to reboot the system if it hung for xxx number of minutes, and be able to look at a log to see if/where things hung up. So, in my travels I saw something called Bootmgr. I placed a copy of the file into the directory with Main Ops.bws in it, and configured it. Then I placed a shortcut to it in the Startup menu. After a reboot, bootmgr started itself up and proceeded to count down. However, it never started Main Ops.bws even though I specified for it to do so. My question is, is bootmgr designed only for .exe and .vpb scripts? And if so, how can I use the .bws and still have it reboot when it hangs up so that it continues where it left off? Any help would be appreciated. Whitney Leach Information Services Rutland Regional Medical Center 802-747-3629 [EMAIL PROTECTED] This message (and any included attachments) is from Rutland Regional Health Services and is intended only for the addressee(s). The information contained herein may include privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail. Thank You
