Subject Interbase/MIDAS. Selecting Server/DB at run time (2)
Author Guillaume JUSTIER
Thanks for your reply. your idea works depending on how the server side is
I have create one server DLL for each module (CUSTOMER, DEALER, CONTRACT).
Which means that they don't "see" each other.
So if I create a module USERLOGIN, USERLOGIN won't be able to change the
server/db on the other modules.

So first of all, is there any advantage in doing what I have done, or am I
better off with only one big server side DLL ?
Because with only one DLL, using a IBConnection component, I would just have
to change its properties to connect to where I want, wouldn't I ?
I would by default connect to a DB called LISTOFDBAVAILABLE, which would
contain well, the list of all my servers,databases, and the user could pick
up his choice as Hans suggested.

I was thinking it would be more efficient to create more small DLLs, but I
am not so sure now...
Sorry about that, but this is my first C/S project, and my first with
Interbase, so there is a lot to take on at the same time.

Thanks in advance,


>>Subject: Re: Interbase/MIDAS. Selecting Server/DB at run time

>>Just a thought

>>As one of the tables on your server site, could be a list
>>of Generic Names <-> Physical Names + any other physical
>>attributes. This table plus possible combined with some
>>User Login table makes up your initial connection DataBase.
>>Now the Client, after passing the user requirement can select
>>the Generic Name and the Thin Server/Client fun can start :)

>>I do something simular, using Asta ThinServerClient products instead of



Guillaume JUSTIER wrote:
> Hi all,
> I am using MIDAS with IBObjects 4 that I just purchased.
> I have a (stupid) problem with my application :
> In the old days of BDE and fat client, I had an INI files with a list of
> server/databases on each client, and they could select which one to
> to (usually a LIVE or a TRAINING database). I was then just changing the
> TDATABASE component and I was connected.
> Now that I moved to C/S with Interbase and MIDAS, how can I reproduce this
> principle ?
> My problem is :
> there is nothing interbase on my client (that was the goal) as all my
> ibojects are on a midas module on the server. I would like to be able to
> select a different database at run time. I simply don't know how to
> implement this.
> I suspect it is something that some of you must do every day, so I would
> appreciate some help to decide which is the best design.
> Thanks in advance,
> Guillaume.