Humm...

Sorry to tell you that the ZEBEDEE solution just have been tried and
failed.

After a few setup trials, I managed to send 2 records! but it
crashed during the transfert of the 3rd one, still with the same
errors (10054/10061).

it was a nice try that proves that the problem is indeed at the
transport level. Does anybody knows of some kind of limitation at
the TCP level for windows 2000 ? I dont think it's really related,
because I use TCP between the client and the server, and it works
very well, even with 30 megs records. but who knows?

So the matter is still open for any body to pitch in. I'm ready to
accept and try any solutions proposed, even it it might sound silly
on the sides. ;-)

TIA,

Spou

--- In firebird-support@yahoogroups.com, Luca Lafranchi
<luca.lafranchi@r...> wrote:

> Two minutes after posting my message I realized that you weren't

talking

> about compression on transfer but on storage :)
> In fact you're right, zebedee has nothing to do with storage of

data,

> but since the original post talked about network errors which

occurred

> when transferring big data, maybe my zebedee suggestion is still a

valid

> one :)
>
> Luca
>
> > I may be wrong but it only does compression at the transport

layer not the

> > storage layer
> >
> > Alan
> >
> >