Subject Re: [firebird-support] Problems with local drive
Author Manuel Aragoneses
Doug, many thanks once more.

I do have de Delphi app sorce code.

On a Data module, I have two TIBDatabase components: one with its databasename property like \\server\d:\data\DBFILE.GDB and the other one with its databasename property like "C:\MyApp\LOCAL_DBFILE.GDB". There is one point where the program needs to access both database files simultaneously. In some computers, it works OK, but in the others, when the program reaches this menu option and tries to open the local database, an exception is raised with the message "Database not available". I know it can reach the remote database file because it works normally in many other procedures that read and write on the server.
Could I make myself a bit clearer? Sorry for being so clumsy... I am still new in these affairs.
Thank you. Best regards.

----- Original Message -----
From: Doug Chamberlin
Sent: Monday, December 22, 2008 1:17 AM
Subject: Re: [firebird-support] Problems with local drive

The way Firebird works is NOT using shared file access the way a file
server shares files. If that is what you are attempting then it simply
will not work.

Instead, the clients communicate across the LAN with the Firebird
program running on a single database server machine. The clients usually
do not directly see the database file itself and if they can see it on
the "file server" that is irrelevant.

The only way the clients can use Firebird to access local databases is f
they are each also acting as Firebird servers. In that case, they would
each have the full Firebird software installed on them, not just the
Firebird client.

So, I am still confused about what is actually going on here.

What is the name of the database file on the server and where is it
located (the full path)? And what is the name of one of the local
databases files?

Also, is this Delphi program one which you have the source code for?

__________ InformaciĆ³n de NOD32, revisiĆ³n 3709 (20081220) __________

Este mensaje ha sido analizado con NOD32 antivirus system

[Non-text portions of this message have been removed]