At 09:40 PM 14/04/2006, you wrote:

>Hi All:
>I googled firebird scripting etc...
>Seems like a script is a batch program that is written in some language like
>Python or other language, compiled and run like a .exe program.

No. Yes. No.

>What scripting language should I look at for my Windows XP environment?

DDL scripts, written in Notepad. DOS batch files, with command-line
calls to isql to run (-input) the scripts. This takes care of the
metadata creation.

>I need a script, or program, to run FireBird, execute DDL, DML and SQL
>statements and output all messages and output to a txt type file. it seems
>I must avoid command line activity. It's just not going to work with my
>screen reader.

You don't need a script to run Firebird: just set it up as a service
and it will be waiting for you. Down the track, when you have
applications to run, you can use the embedded server for single-user
deployment - again, nothing to do to "run firebird" - you don't even
change any program code if you do it right.

You'll need a programming interface (programming language plus data
access interface) with which to write your applications. Basic +
ODBC is one. Python + KinterBaseDB is another. PHP + its
Firebird/IB extension is another, Java + the JDBC Jaybird library is
another, C++ with IBPP is another....and so it goes on.

If you are using these non-visual tools, it's going to be fairly hard
to avoid the command line at some point. Python might be a good
pick, if you're bracing yourself to learn a new language. It's much
richer than Basic, it's free, and it does have a text-based IDE.

>Most languages referred to Linux cgi scripts;

You can write cgi scripts in just about any language. They are for
web applications. You need to be running a web server, such as
IIS/PWS, Apache or OmniHttpd to execute cgi scripts.

>Windows scripting seems to be for VBA or other .net applications.

Microsoft has various sorts of Windows-only scripting, all based on
VBScript. But Microsoft's [in]famous tools are neither your only nor
your best choices. VB.Net is for .net applications but other
flavours are non-dot-net.

You seem to be looking at least three rather steep learning curves
here: SQL, a programming language and client/server
development. Maybe four, if you are throwing CGI into the mix and
are intending to write web applications, having only written desktop
apps for ISAM databases previously.

But first, you need a database - the means to create one and the
means to maintain it. In your shoes, I'd focus first on arriving at
some means by which you can administer (create, maintain) your
database and test DML statements.

For more suggestions I'll contact you off-line.

./heLen