Question: How to connect to a remote Firebird server using FIBPlus?

Answer: We will demonstrate this using a server called acmeserver and a database file called employee.fdb. The application has to be deployed to several users that will access the server across a network. Here's how to do this with Firebird 1.5/2.0 and FIBPlus:

STEP 1: CONFIGURE THE FIREBIRD SERVER

  • On the server where Firebird is installed you should navigate to the directory where Firebird is installed.
  • Open file called "aliases.conf" (use notepad to do this)

  • The alises.conf file contains aliases (shortnames) to where a database is located. So we have to add an entry for the employee database so that application can use this alias to connect to it across the network. There are two parts to every entry in the alises.conf file: <alias>=<db location and name>
Add the line:

EmployDB=C:\Program files\Firebird\dbs\employee.fdb


  • Save the file. Notice that Firebird should be restarted; the alias is picked up instantaneously.
  • You can add as many aliases as you want for the database and as many entries as you want for any number of databases.

STEP 2: CONFIGURE FIBPlus TpFIBDataBase COMPONENT:

  • Open up the database editor by double clicking on the TpFIBDataBase component
  • Click on "Remote Server". This means that we will be accessing the database from the network.
  • Make sure that "TCP/IP" is selected for the network protocol.
  •  Select the database alias which you want to use in the editbox next to the database type in the database. In this case it's  EmpoyDB.
  • Type the user name in the database. In this case it's SYSDBA.
  • Type the password in the database. In this case we use masterkey.
  • Ensure that 3 is selected in SQL Dialect .
  • Always ensure that the client library points to a valid client library.

Preview text: 
Prices in Euro:

235 (1 copy)
1250 (unlimited)
Volume discounts are available...

Navigation



We are a small software company with thousands of customers delivering comany wide systems including accounting, logistics, e-commerce, POS, sales etc etc. Several years ago, when we were still a very small company, we used Delphi 3 and Paradox combined with BDE. As our system (and customer base) grew I decided to switch to Delphi 5 and Interbase. Being a huge improvement over Delphi 3 and Paradox, I encountered numerous problems with IBX: memory leaks, performance issues and other problems. Borland was not to be bothered: IBX was provided "as is" and no support was avaliable. 
Not being very eager to use third party components with Delphi at first, I decided to give FIBPlus a try. At once all problems where gone: no more memory leaks and  performance was very consistent. 
But the real advantage of switching to FIBPlus came with the upgrade to D2005: after upgrading there were some problems with the new FIBPlus version. After emailing the problem I received an update within an hour! And this was at 11 pm! A few other (smaller) errors where handled in the same way. 
Our motto is: software is as good as its support. And support of Devrace is just great!
Just a little indication of our FIBPlus use: all our software runs 100% on FIBPlus. Our customers have a total of aprox. 4.800 Firebird databases in production, with a combined size of over 130TB and over 80 million transactions a day. Every
day. And FIBPlus has not failed a single transaction. Not once. There is, however, one (minor) drawback in using FIBPlus: while debugging an application which uses and invalid SQL instruction, de Delphi Debugger returns to the FIBPlus code instead of to our calling code (where the actual error comes from), thereby complicating de debug proces a little. But that is a very small price to pay for a otherwise brilliant third party solution! >>

Bas Jordans JorSoft Ltd
FOR CUSTOMERS
Download full versions and updates in your Personal Area