I did this as a convenience but a person really should use the Database
property for this and reserve the DatabaseName property for the more user
friendly way to refer to a database.

The way this started is I had the DatabaseName property reflect the fully
qualified database connect string if the user friendly one wasn't provided.
People somehow got the idea this was where you assigned the value and so it
just stuck.

Jason Wharton

----- Original Message -----
From: "Andreas Bednarek" <andris@...>
To: <IBObjects@yahoogroups.com>
Sent: Thursday, October 23, 2003 2:13 PM
Subject: [IBO] Setting TIBODatabase.DataBaseName property


> Hello everyone,
>
> in a recent thread here I realised, that setting the DataBaseName property
of TIBODatabase component is not recommended and there was a reason for it.
Now I will speak here about two database connections, remote and local
(anybody has more ideas? :-).
>
> I found out that setting this property to a local path like:
>
> DataBaseName := 'd:\MyApp\data.fdb';
>
> Automatically sets the other properties this way:
> Server := '';
> Protocol := cpLocal;
> Path := 'd:\MyApp\data.fdb';
>
>
> Setting DataBaseName to a remote path like this:
>
> DataBaseName := 'HPComp:D:\MyApp\data.fdb';
>
> sets
>
> Server := 'HPComp';
> Protocol := cpTCPIP; //fortunately :-)
> Path := 'd:\MyApp\data.fdb';
>
>
> Well, seems like it works the intelligent way. Anybody has suggestions
about setting that property be good or bad?
>
>
> Thanks
> Andreas
>