At 07:03 AM 14/04/2006, you wrote:

>Good Evening Gang:
>Well, I learned allot.
>What's working:
>start, run, cmd:
>cd c:\Program Files\Firebird\Firebird_1_5\bin
>enter
>isql
>enter
>The ISQL Shell comes up
>I've been entering the connect statement to the example employee.fdb
>billions and billions of times, at least Carl Sagan might have put it that
>way. When everything is re-typed perfectly, I hit enter and hear nothing.
>Whenever there is an obvious error I get an error message so I guess hearing
>nothing from my screen reader might be a good thing.
>I can't navigate up and down to re-type lines,

The lines are buffered, so you can retrieve the previous line typed
(and the previous before that, and so on) by using the up and down arrow keys.

>and if an error occurs can't
>get to the SQL> prompt without quict (sometimes it works) most times I have
>to re-boot to get out of an error statement.

To kill a command program on Windows, use Ctrl-C.

If ISQL is not hung (as might be the case here) you can also open a
new command shell using the command

SQL> shell;

But, if things go quiet after typing an ISQL command, it might be
that you forgot to terminate the command with a semi-colon. In that
case, the CON> prompt will be showing, waiting for whatever comes next.

>So that's it for today. Is there a way to do this with a script, something
>else I've never done but if writen in notepad will be accessible to my
>screen reader more easily and eliminate all the re-typing.

You *can* write a script consisting of DSQL statements (including
COMMIT if needed) in any ascii text editor and run a command-line
isql command using the -input <file path and name>.

>Tomorrow I'll dig into the user manual for isql to see if there is anything
>there.

The ISQL documentation is in the Borland IB6 beta book
OpGuide.pdf. But I'll send you some stuff offline today that should help.

./heLen