At 04:03 AM 22/04/2006, you wrote:

>Hi All:
>The Following script is being loaded, will run, create the output file but
>the output file is empty.
>Any Suggestions?
>/* Start Script */
>OUTPUT C:\RtFbISQLLog.rtf ;
>HELP ;
>OUTPUT ;
>QUIT ;
>/* End of Script */

When writing to an output file, ISQL filters the output so that
"extraneous" ISQL commands that are not database access
statements don't get sent to the file.

When it encounters OUTPUT, SHOW <something>, EXIT, QUIT, and some
(though not all) SET <something> commands, which are all commands
specific to ISQL's own workings, it knows not to output them to the
file (which works properly about 99% of the time). Then, when
executing the file as an input file, if it comes across any
statements containing its own internal commands, it just no_ops them.

That's what is happening here. It's all fine for the script to
create and open the output file, but the script terminates without
having anything that ISQL encounters that has to be written to the file.

On the other hand, if you invoke isql with a combination of switches
that DOES have something ISQL can write out, your file won't be empty!

c:\Program Files\Firebird\Firebird_1_5\bin>isql -ex -t
"%%" "c:\program files\firebird\firebird_1_5\examples\employee.fdb"
-o c:\efgh.txt

./heLen