Karen, Does your scheduled task have a log in user with enough rights? Could Windows security be protecting you from yourself? I found a situation where after a recent Windows server update, Windows was killing two batch processes that ran "unknown" exes, including rbg76.exe or rbg80.exe. I had to put them in a trusted list.
Bill On Thu, Dec 4, 2008 at 1:48 PM, <[EMAIL PROTECTED]> wrote: > I'm sitting here with another consultant. We have a pretty big piece of > batch processing code that can be run from within a 7.6 form. It takes 1 > minute to run, which the client is happy with. > > However, we also want to call this exact piece of code in a scheduled > task. He uses a batch file that calls 7.6.exe passing the program name to > run. This program simply runs the code I mention above, followed by an > EXIT & RETURN. We see 2 problems: > > 1. RBase does not exit; it hangs. If we manually close it, then it > continues with the rest of the batch file. > > 2. The code itself takes about 10 times slower to go through from within > the batch file than it does when run from the form. > > Has anyone any experience with running from a batch file? > > Karen >
