At 09:48 AM 17/02/2011, Matthew Adams wrote:

>Make sense?

Not really; but I don't have time to go into it. I hope you eventually get some kind of answer that is acceptable to you, though.

>It seems to me that I should be able to either set
>everything that's in firebird.conf via the .NET provider's connection
>string

Pretty doubtful assumption. A connection string relates to a database connection, not the server configuration. When you write client applications your provider is wrapping calls to the client API, which is the medium through which applications make requests to the engine. The API doesn't have the facility to bend and twist the server engine. Firebird.conf is a server asset: it configures the server's behaviour. There are certain global settings in firebird.conf (such as the default page cache size) that can be overridden in the DPB by a privileged user so, if you could make your questions to the dotNet list more specific, you'd be able to find out whether whatever it is you want to do is implemented.

>, or the .NET provider connection string should provide me with a
>setting to tell it where to find (absolute or relative pathname) the
>configuration file, which I'd prefer to not have to be named
>"firebird.conf".

Not supported in the API; can't comment on what the dotNet provider can do beyond the bounds of the API.

./heLen