At 09:34 AM 13-08-01 +0200, you wrote:

>Hi all,
>
>just another migration issue.
>
>The IBX connection path is stored within one property
>(TIBDatabase.DatabaseName) for local (C:\test.gdb) and remote
>(ntserver:c:\test.gdb) connections whereas IBO has three properties Path,
>Protocol and Server. How can I convert an IBX remote connection path into a
>IBO proper syntax?

IBO connects all the pieces up and makes the appropriate path. What goes through in the connection string depends on the Protocol property. Path must contain only the absolute physical path name **as seen from the root of the server**. If you omit the Server property, IBO will force a local connection (cpLocal). If you include the Server property and select cpTCP_IP or cpNetBEUI, IBO will construct the proper connection string. If the Server field is supplied and you select cpLocal, IBO ignores the server name; so, if you want a local TCP_IP loopback connection (recommended for a local server) make sure you enter LOCALHOST into the Server property and select cpTCP_IP.

To see this process at work, leave the DatabaseName property blank - the full connection string will appear there. You'll override this behaviour if you put a custom name (i.e. an "application alias for the connection") into this field; but this doesn't affect the string that IBO constructs internally.

Regards,
Helen

All for Open and Open for All
InterBase Developer Initiative · http://www.interbase2000.org
_______________________________________________________