From: <jmashburn2@...>
Date: 2007/01/15 Mon PM 07:52:49 EST
To: <firebird-support@yahoogroups.com>
Subject: Re: Re: [firebird-support] Firebird Server Access

Thanks for the response. I finally figured out the syntax using iSql on both machines. Part of the problem was that I am more used to accomplishing those task in code using MySQL and PostgreSQL. I only resorted to the text tools to try and understand why I was unable to connect using ODBC in code. Now that I have figure out GSEC & iSQL I can now get back to trying to accomplish the same thing in VB 6 code. If you know of any pitfalls I might run into I would appreciate a heads up. I have down loaded both the ODBC and the OLEDB IBProvider so tomorrow I hoping to get into some serious code.

I am investing the time to familiarize myself with Firebird because it provides both an embedded DB and a Client/Server DB. I have been using MSAccess, MySQLl and PostgreSQL to offer scalability to my applications if I can accomplish the same thing with Firebird my life will become much easier.

Thanks again for the input.


dkoder2

>
> From: Helen Borrie <helebor@...>
> Date: 2007/01/15 Mon PM 07:00:15 EST
> To: firebird-support@yahoogroups.com
> Subject: Re: [firebird-support] Firebird Server Access
>
> At 03:09 AM 16/01/2007, you wrote:
> >I have installed Firebird 2.0 on both a W2K and Linux (Fedora 4)
> >Servers.
>
> [ ..snip.. ]
>
> >The connection string examples I have found on the internet for
> >connecting to TCP/IP Client/Servers include the drive letter. I find
> >that rather odd since normal TCP/IP connections require either the
> >host name or IP Address. I don't understand. Unix(s) don't use drive
> >letters at all and the nearest example I've found is <host>:<database>
> > which generates error on both the W2K Server or the Linux Server. I
> >confused, frustrated growing more anti-Firebird by the minute. Could
> >someone please point me in the right direction? Surely I not the only
> >one to have this problem. (and then again...).
>
> OK, the "right direction", if you are a newbie at Firebird,
> client/server and/or cross-platform computing (and it seems you are
> all three) is the Quick Start Guide, which you should find in the
> /doc directory of your server installation.
>
> You are using a Windows client to access a Linux server. You need a
> Linux path because, as you observe, Linux doesn't understand Windows
> paths. The path should always be a fully-qualified path to a file
> *as seen by the server*. (It cannot be a share of any sort, such as
> a Samba path!) And, because your client has to access a Linux server
> across a network, you need a properly constructed TCP/IP connection
> path. That's why you have to include the hostname in the connection string.
>
> Briefly, suppose server's network name is 'linuxsvr' and your
> databases live in a directory called /home/firebird/databases, for
> which the linux system user or group 'firebird' has all the necessary
> privileges. You want to connect to a database there with the file
> name 'mydatabase.fdb'. Here's the connection path you need from your
> Windows (or Mac or Solaris or whatever) client:
>
> linuxsvr:/home/firebird/databases/mydatabase.fdb
>
> For specific issues concerning your database drivers, you should
> subscribe to the relevant support lists (firebird-net-provider and
> firebird-odbc-devel, respectively) and ask there. You can subscribe
> to these lists directly from this page:
>
> http://firebirdsql.org/index.php?op=lists
>
> ./heLen