Except Helens notes were on the IBObjects list so I have copied them
over.
This must exist as a FAQ somewhere?

The Networking chapter of the Ops Manual has the instructions.

You need to know the network (IP) address of the server, e.g. 10.0.0.1
or some other
IP address that has been set up by you network admin.

On the Win98 clients, you need an entry in the HOSTS file for the
server. Search
/windows/system32 (or thereabouts) for HOSTS. If you don't have a
HOSTS file, copy
HOSTS.SAM and rename it HOSTS. Don't move HOSTS to a different folder.

You need a name for the host - IB doesn't like to connect to an IP
address, even
though it can under some circumstances. If your NTWS doesn't have a
server name,
just make one up, e.g. OURSERVER.

Type a line inside your HOSTS file as follows (assuming the examples I
used here):

10.0.0.1 OURSERVER # Host for IB Server

Save the changes.

Now, your IB client will be able to connect. Make sure the client has
the TCP/IP
prototcol at the top of your Windows Networking protocol list.

The full connect string is exactly as follows (don't omit any
backslashes):

OURSERVER:c:\path1\path2\OurDB.gdb

of course substituting the physical path of the gdb file on the server
machine. YOU
CANNOT USE MAPPED DRIVES. It must be the actual physical path.

When setting up an IB_Connection, you would chose tcp-ip for Protocol
property, enter
OURSERVER in the Server property and c:\path1\path2\OurDB.gdb in the
Path property.

Cheers,

Helen
--
Lester Caine
-----------------------------
L.S.Caine Electronic Services