At 08:00 PM 02-08-01 -0600, you wrote:

>Im not doing a DNS lookup, just simply 192.168.0.2:c:\mydatabase.gdb.
>It does seem to work fine once connected.

This is not recommended. If your network doesn't use DNS then just create an entry in the hosts file with any server name, e.g
192.168.0.2 IBSERVER

>In fact, its even slow when on the same machine with the IP of 192.168.0.2.
>Wierd. If I use local host (which I assume uses Netbeui)
>It loads much faster..

LOCALHOST is a default server that exists on your local machine with an IP address of 127.0.0.1.

If you connect using a TCP/IP string, it makes a TCP/IP connection (recommended). If you connect using a NetBEUI string, it uses Windows networking which is both noisy and slow.

Here is a TCP/IP string:

MYSERVER:c:\databases\mydata.gdb

Here is a NetBEUI string:

\\MYSERVER\c:\databases\mydata.gdb

The golden rule is - although you CAN, don't use a raw IP address to connect. I don't know why this recommendation exists but it's documented and the archives show a lot of people reporting problems from it.

I guess you also know that connected to a Windows mapped drive is a No-No.

btw, whatever you do, never let any client connect with a string that omits the backslash after the physical drive designator. This is a known cause of the kind of data corruption that you have to pay an expert to fix. Jason made IB_Connection reject a connection string in this format but other clients based on the BDE, IBX, etc. won't stop you.

regards,
Helen

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