>
>It could be just that the BDE doesn't work well on Win2003. Borland
>deprecated the BDE after Delphi 5 and the half-hearted "upgrade" that
>shipped with Delphi 6 was ...erm... not a bucket of thrills. The Delphi 3
>BDE version is ancient - one of the very early 32-bit versions.
>
>Have you tried connecting remotely using isql? (not WISQL, but
>command-line isql). It doesn't use the BDE, so at least you could
>establish whether it's the BDE that's your problem.
>
>heLen

I know this isn't the place for it - but heLen is 100 % correct. There were
several large changes between Delphi 3 and Delphi 4. The biggest change was
in the data objects (TTable, TQuery, etc) and in the BDE. At the same time,
the BDE itself was effectively rewritten ...

I was developing a very large credit control application at the time on IB
5. We achieved access times of under 3 seconds, on average, to return a
record from a 2 GB DB over a WAN using a dedicated 64 k diginet line. The
server was sitting 1 500 km away, and running NT 4 SP 1 on a duel processor
P II. We had about 200 clients accessing the DB over the WAN, using Win 95
SP 1. And we had no problems with connection speed.

We had a significant (about 35%) speed increase using D4 rather than D3.
But we had to delete ALL the data components and replace them with the D4
components. We also had to make sure that we applied the D4 patch, which
IIRC was a large one (35 MB?) The components have to be replaced, for some
reason that I have never completely understood, but which had to do with
the D3 code staying around unless you deleted the component. We couldn't
just recompile under D4.

So what I am saying is that it can be done, but :

You need D4.
It involves some work.
AFAIK, FB 1.5 is still being tested on W2003. I don't know about IB 7.

BTW - that project was the one that made me fall in love with IB ...

Regards

Tim


[Non-text portions of this message have been removed]