Marco Antonio Abreu wrote:

> Hi guys,
>
> I have a "little big" problem with Firebird's aliases and configurations.
>
> I'm developping a system that runs in windows stations, but the FB

server may be running in another windows PC or in a Linux one.

>
> - The Firebird server may be installed by the network

administrator, installing FB server in many different directories;

> - The users can only access they own PC, not the server;
> - Applications and users may don't have a way to know where the

database is in the server, except the server name;

> - The database must be shared with all stations where the same

program have been installed;

> - The database cannot be created in operation system directories

(like c:\windows\system32\ or /usr/bin/);

> - The full system will have some databases, one for each module

and one general, because some modules are optional or independent;

> - I can use SYSDBA to create the databases;

Using aliases.conf and firebird.conf will probably solve all your
problems - although I may not have understood your specifications correctly!

Create aliases (on the server, of course) like:
PROD = D:\DB\production.fdb
ANALYZE = E:\DB\analyze.fdb

Let SYSDBA create the databases. The users should not have any
access to the server (except through the tcp/ip connection to the
firebird server).

Your client machines (pc's) can now access the databases (assuming
the server is named DB_SERVER) with DB_SERVER:PROD and DB_SERVER:ANALYZE.

Making aliases available without knowing what the databases are to be
used for doesn't make much sense. Either put the aliases into the
applications (or have them read from e.g. an ini-file) or make a list
of databases (aliases) for the users to choose from.


--
Aage J.



<<
There is some kind of resource or configuration to especify the
default directory to create all databases in a Firebird server?

>>

Don't think so.
Rather, set the firebird.conf so that _only_ aliases can be
used (don't allow applications to use path\filename).


<<If don't, I supose it may be a good feature to be present in next
versions. To work well it's necessary only about four services
(CREATE ALIAS, ALTER ALIAS, DROP ALIAS and LIST ALIASES) or two
directives in the firebird.conf file like "AUTO_ALIASES" and
"DEFAULT_DATABASE_DIR". When a new database is created or dropped the
aliases.conf file shold be automatically updated with its file name.
The second directive must be defined when the first one is ON/TRUE/1...

>>

Forget about this :-)