How to connect to Firebird from Database Desktop in W64
lazarus / 5-Lazarus Extra Components

----------------------------------------------------------------------
janasoft · 2012-08-05 09:50

Hi, everyone.
I run Lazarus in W64 and when I have compiled the Database Desktop
I've seen that is not posible to connect to Firebird Databases
directly, but only via ODBC (even this option I haven´t tested). In
W32 the conection can be made without problems.
I'm a beginner in Lazarus and perhaps there will be a obvious reason,
but I've searching for in the forum and I haven´t found any topic
about this behaviour.
Could you give me some information about this?
Regards

----------------------------------------------------------------------
exdatis · 2012-08-05 12:49

Try:
Control Panel->System->Advanced system settings->Environment variables
and in System variables - path click edit, add path to Firebird bin
directory(e.g C:\Program Files\Firebird\Firebird_2_5\bin), restart pc.
Regards.
p.s. Also see:
http://www.lazarus.freepascal.org/index.php/topic,17741.0.html
(problem with firebird.config),maybe put path to config file with
environment variables?

----------------------------------------------------------------------
marcov · 2012-08-05 14:26

Probably the client library must match.

So if you generate a 32-bit binary, you must have the 32-bit client
dll (fbclient.dll), and if you have a 64-bit one, you need the 64-bit 
client dll.

----------------------------------------------------------------------
janasoft · 2012-08-05 15:27

Quote from: exdatis on August 05, 2012, 02:49:03 pmTry:
Control Panel->System->Advanced system settings->Environment variables
and in System variables - path click edit, add path to Firebird bin
directory(e.g C:\Program Files\Firebird\Firebird_2_5\bin), restart pc.
Regards.
p.s. Also see:
http://www.lazarus.freepascal.org/index.php/topic,17741.0.html
(problem with firebird.config),maybe put path to config file with
environment variables?
Thanks for your answer, but perhaps I explained in a bad way. I have
no problem to work with FB inside Lazarus, nor accesing to the
Databases from another clients (i.e. Workbenh) It only happens inside
DataBase Desktop.

I've searching in the code and It seems that is expressly not permited
in W64. I attached some lines of frmmain where, I think, are declared
the Databases permitted.
Code: [Select] // Data dictionary support for
  fpdddbf,     // DBF
  {$ifndef win64}
  fpddfb,      // Firebird
  fpddmysql40, // MySQL 4.0
  fpddmysql41, // MySQL 4.1
  fpddmysql50, // MySQL 5.0
  fpddoracle,  // Oracle
  fpddpq,      // PostgreSQL
  {$endif}
  fpddsqlite3, // SQLite 3
  fpddodbc,    // Any ODBC supported [/quote]
If this is right, I wonder what's the reason?

Regards

----------------------------------------------------------------------
janasoft · 2012-08-05 15:37

Quote from: marcov on August 05, 2012, 04:26:52 pmProbably the client
library must match.

So if you generate a 32-bit binary, you must have the 32-bit client
dll (fbclient.dll), and if you have a 64-bit one, you need the 64-bit 
client dll.

Like I've told to exdatis, I think I have no problem with the clients.
I forgot to say that I've checked DB Desktop in two devices: one with
W64 and another with W32, each one with its own client. In the device
with W32 everything is fine and in W64 only is possible acess to DBF,
SQL lite and ODBC.

In any case, many thanks for your answer.

----------------------------------------------------------------------
ludob · 2012-08-05 16:36

Until recently, several database connection components where not
available on win64, mainly because the client libraries where not
available.  Because client libraries are loaded at run time, the
restriction on the availability of db connection components has been
relaxed a bit and now most components are available. So probably
DataDesktop applied the same restrictions as lazarus a while ago. If I
where you I would remove the  ifndef win64 and give it a try.
There are some known problems with the postgres 64 bit client and
exceptions being caught in fpc instead of the library. The pop up as
"Ctrl C entered" exceptions. On the mantis bugtracker, there are
several issues opened and some workarounds described.