At 10:00 PM 14/06/2004 -0400, you wrote:

>I am used to installing IBO C++ Builder programs on 98 or Win2000. I
>have donated a membership program to a Church. They are testing it on
>XP professional as a local server. It takes forever to log in to the
>server, Interbase 6.02. At first I thought it was locked up but on the
>second or third time I waited and it opened in 2 or 3 minutes.
>IBConsole and IBO Console exhibit the same behavior. I named the
>database *.GDC to avoid the *.GDB problem with XP is there something
>else I should consider?

Try "*.IB" as your suffix (Borland's recommendation for InterBase databases
on XP). It's probable that "gdc" is in System Restore's hit-list too.

Also, don't overlook the fact that IBO downloads metadata right at the
beginning of a connection. It shouldn't take more than a few seconds,
though. And, if you are using TTables or select * queries and you have
these opened by FormCreate, that's going to slow down even a local
connection - though the reasons for slowdown are different for local than
for remote connections.

>Does the Remote Server exhibit the same
>difficulty?

Erm, actually, IB 6.02 is full of bugs. If you must use it, don't use
local connect for anything but the command-line tools (gbak, gstat, gfix,
etc.) Use the TCP/IP local loopback: set your IB_Connection's Server
property to localhost and Protocol to cpTCP_IP; with third-party tools use
the path "localhost:d:\databases\MyDb.ib".

> What other XP problems should I look out for?

With IBO, none in particular.

There are various niggly problems with Windows platforms - best to wait and
see if you get any weirdnesses and post a suitable question in
Firebird-support (not here, please). Firebird-support will help you with
IB 6 problems up to a point...but the most likely (and best) advice you'll
get there is to drop IB 6 and use Firebird. IB 6 is old and unmaintained
and it never was more than a beta.

Helen