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, 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.
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.
Tomorrow I'll dig into the user manual for isql to see if there is anything
there.
anyway:
Thanks for the help and have a nice evening all.
Rick Farmington Mich. USA

----- Original Message -----
From: "Helen Borrie" <helebor@...>
To: <firebird-support@yahoogroups.com>
Sent: Thursday, April 13, 2006 9:22 AM
Subject: Re: [firebird-support] Connect to Sample FDB


> At 10:25 PM 13/04/2006, you wrote:
>>Good Morning Gang:
>>
>>Today I'd like to connect to the Employees sample Db and play with it
>>some:
>>
>>Here is my general plan with a couple of basic questions.
>>
>>The only real question is how I verify the User and Password for the
>>database in Windows XP but sometimes assuming anything when learning can
>>cause headaches so here is the plan with a couple of embedded questions.
>
> It's not specific to Windows - the username and password belong to
> the firebird server, whatever host it is running on. Use SYSDBA and
> masterke for now.
>
>
>>Step ONE:
>>
>>I went to the bin directory and clicked ISQL.exe:
>>
>>The SQL window came up and I entered:
>>
>>quit;
>>
>>the window closed.
>
> Lucky, but actually you need to run the command-line utilities
> directly from the - well - command line, i.e. open a command shell
> from Start > Run. Tip: make a shortcut that takes you straight there
> (I call mine "Command-in-bin").
>
>>Step Two:
>>
>>connect to the
>>
>>"C:\Program Files\Firebird\Firebird_1_5\examples\employee.fdb"
>>
>>DataBase.
>>
>>The Connect Statement:
>>
>>SQL>
>>
>>CONNECT "C:\Program Files\Firebird\Firebird_1_5\examples\employee.fdb"#
>>
>>CON>
>>
>>user 'SYSDBA' password 'masterkey';#
>
> Yes. Except, if you are using Classic you need to connect through
> the localhost server:
>
> SQL> CONNECT "localhost:C:\Program
> Files\Firebird\Firebird_1_5\examples\employee.fdb"#
> CON>user 'SYSDBA' password 'masterkey';#
>
>
>>Rick:
>>
>> >From Quick Start:
>>
>>user:
>>
>>Administrator was mentioned as user for windows so:
>>
>>SYSDBA or Administrator
>
> No, not Administrator - unless you create a DB server user named
> Administrator. But until you get your head around SQL privileges,
> stick with SYSDBA.
>
>>Is there a way to check My User Id and Password for a Fb DataBase on
>>Windows
>>XP?
>
> Username - yes, once you have successfully logged in.
>
> select cast(current_user as varchar(31)) from rdb$database;
>
> Password -no. Even the SYSDBA can't retrieve anyone's password. If
> don't have a good memory, you'll need to keep paper records of passwords.
>
>
>>Rick: Blurb in Quick Start:
>>
>>if Firebird runs as this user) needs also to have permissions to objects
>>inside a database.
>>
>>Rick: don't fully understand, later research if not required to play with
>>Employees DB to verify today's connection.
>
> Definitely for later research. SQL privileges are a nest of
> (eventually necessary) vipers.
>
>
>>We will look at authenticating as SYSDBA using the password masterkey.
>>
>>Rick This is why I'd like to verify the User and Password before hitting
>>enter.
>
> You verify the password for the supplied user name by submitting a
> connection request. If it fails, you know that you have one of them
> wrong.
>
>
>>At this point, isql will inform you that you are connected:
>>
>>DATABASE "C:\Program Files\Firebird\Firebird_1_5\examples\employee.fdb",
>>
>>User: sysdba
>>
>>SQL>
>>
>>You can now continue to play about with the employee.fdb database. The
>>characters
>>
>>To get back to the command prompt type
>>
>>SQL>QUIT;#
>>
>>EndOfPlan:
>>
>>If everything works, meaning I can use the command line Input and Output
>>for
>>experimentation, I'll dig into the manual to explore other interactive
>>commands and utilities before trying to connect from within a Liberty
>>Basic
>>program. .
>>
>>Does this plan sound OK?
>
> Sure. Remember, ISQL is just a client application. Theoretically,
> if you can connect to your server installation using ISQL, you can
> use the same connection parameters to connect from any
> application. Where it gets interesting is that different drivers
> have their own ways of playing about with the connection
> parameters. ODBC (which I understand you are planning to use with
> Liberty Basic) is no exception to this rule.
>
> ./heLen
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>