At 11:03 AM 4/04/2004 -0400, you wrote:

> > OK, what you were asking before doesn't marry with what you are talking
> > about here. Now you want to use two completely different client versions
> > inside a single app to connect to different server versions?
> >
> > Helen
> >
>
>Ha! I know I'm all over the place on this one. I'm just trying to find a
>good solution to do what I want. I tried using the fbclient.dll (renamed to
>gds32.dll) to connect to both the embedded server as well as a remote server
>and it didn't seem to work. It seems that it has something to do with the
>server property being ignored?
>
>For instance, this does not work:
>// It looks for the database file locally, regardless of what the server
>property is set to
>With IBODatabase1 DO
> Begin
> Server := '192.168.1.200';
> Database := 'C:\mypath\mydb.fdb';
> Connect;
> End;
>
>...while this seems to work:
>
>With IBODatabase1 DO
> Begin
> Database := '192.168.1.200:C:\mypath\mydb.fdb';
> Connect;
> End;
>
>My impression was that the Server property and the Database property were
>concantenated together before connect, but that does not seem to be the
>case, at least using this version of the library. I believe there was
>something mentioned in the release notes about the server property being
>ignored?

Lee, LEE, LEEEEEE!

If you are connecting to TWO databases, you need TWO connection objects.

And you have the information about the pieces of the connection string
scrambled. Use the properties Server, Path and Protocol. Leave the
Databasename property alone. You can change it to some nice, user-friendly
name like "fluffy" or "honeybunch".

If you want to try and use one connection object for both databases, then
you can't do it simultaneously. Put some selector device on your main form
and let the use select the one or the other, pick up the responses and set
those three properties at run-time.

Helen