Subject Re: [firebird-support] Re: Problems with local drive
Author Manuel Aragoneses
Thank you, Adam

I think I have the idea as how data is reached: only through a communication between my app with a "Client engine" which in turn dialogs with a "Server engine" (both Firebird software); but perhaps with a poor English I give the impression of having a hollow concept about it.
Now, I must arrive to the conclusion that having installed the "Server engine" on the file server of the Lan, and also on each client computer, it will be possible for the Delphi program to reach data on both physical databases, even when they are located in different machines, as needed. I thought that the Firebird software was installed in the same way in every client computer, but I must realize now that some of them have the server software running on it and the others don't.

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

--- In, "Manuel Aragoneses"
<exactsoft@...> wrote:
> Thank you, Adam.
> As you can see, I am not enough acquainted of the database engine
> I suppose that maybe in some computers where the Delphi application
can work with both the local and remote databases (I mean the .gdb
files) the Firebird installation produced a Firebird server to run on
those machines, allowing the program to access both physical files (is
it so?)

No, your program doesn't access physical files. That is still the
mindset that a database is a document, and such thinking will confuse you.

A Firebird server accessed the physical files. If the physical files
are on different machines, then they were accessed by two distinct
database servers, each server running on the same physical box as the
hard drive holding the file.

If your client software connects to databases, one on the local
machine and one on a network server, then there must exist a Firebird
server on the local machine, and a Firebird server on the network server.

The Firebird server on the local machine could be the embedded
database engine, but only you can tell us that.

> and in the others, the client software won't grant access to the
local .gdb file, but yes to the remote one.

The client software cant access any file. It relies on a server to act
as its proxy to the database file. If there is no server for the local
file, there can be no access.

> Should I uninstall the engine on the critical PCs and try to
re-install it with a new feature, in order to have all the computers
with a Firebird server running on it?

No, randomly installing and uninstalling things won't help. What is
the "new feature"?

You need to tell us where is the database server that is physically
reading and writing the database(s) that you can not read and write.


__________ 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]