At 11:54 PM 22/08/2003 +0000, you wrote:

>All, (This may have been double-posted, sorry)
>
>Just to see if I have it right...
>
>MACH_A has XP Pro, FB/IB Server S/W and D:\MyApp\MyData.GDB
>
>MACH_B has XP Pro, FB/IB Client S/W (and app programs)
>
>MACH_B IBO database string should be: MACH_A:D:\MyApp\MyData.GDB
>
>Or have I got it ALL wrong somewhere?

Looks good for TCP/IP. Remember that IBO will take care of the correct
string per protocol as long as you set up the Server, Path and Protocol
properties correctly.

And you *can* have NetBEUI in the protocol stack - and will need it if
MACH_A has to participate in peer-to-peer (not a coool idea, but it is
possible). Make sure that TCP/IP is at the top of the stack for both
MACH_A and the clients.

If the server has a server OS and you don't care about performance, you
*could* use NetBEUI for the client/server protocol. In that case, the
clients' connection string would be:

\\MACH_A\D:\MyApp\MyData.GDB

Again, IBO will take care of that if you set the properties correctly.

This *looks like* UNC but it will work only if MACH_A points directly to
the physical host machine.

Need I say that you should avoid using MACH_A for anything other than
database server (in which case, remove NetBEUI from it and have the clients
connect through TCP/IP). Database servers don't like sharing resources
with other apps. They can if they have to, though it won't help
performance. At the very least, don't run screensavers or any other form
of eye-candy on the server...if it's a server OS, keep it logged off when
not in use.

Now we are waaaaaaay off-topic for IBO. If you want to persevere with this
thread and it has no IBO aspect, take it to firebird-support, please.

Helen