In the beta, I’m seeing it not display these errors when you run
from command line, but unfortunately, it isn’t logging them either (unless you
set up the log file option)
Next beta will still not show these errors when you run from
command line, but will always write them to the app designer error log (in
addition to the more detailed import error log, if you configure it)
-John
From:
toad@yahoogroups.com [mailto:toad@yahoogroups.com] On Behalf Of Melanie
Wert Cantrell
Sent: Thursday, July 02, 2009 2:26 PM
To: toad@yahoogroups.com
Subject: [toad] importing in batch using Toad app
Hello, all.
I have a Windows batch job that runs a Toad app which does an import from a
file into a table. When I run the app interactively, if it encounters an error
(e.g. null value for non-null field), I get a dialog window that asks me if I
want to continue. If this happens in batch, the app stops and the job continues
at the next step. I am logging errors, but the load stops after encountering
and logging the first error.
This is the command I'm using
%ToadHome%\Toad.exe -c %DBConn% -a "load temp tables->persons"
Is there something I can add to this that will tell it to continue after encountering
an error?
Melanie